Re: [Savannah-users] Anonymous commit (empty Author and Committer)

[Andrei Borzenkov]

31.10.2015 16:46, Andrei Borzenkov пишет:

31.10.2015 10:02, Andreas Schwab пишет:

Kaz Kylheku  writes:


Nope. They will have a git in which that commit looks like their own
local work. *Someone* will inadvertently do a "git push" to blast out
their changes based on that deleted commit, thereby causing it to
reappear.


Not if another one pushes something different in the mean time.



Which is why I said "amended".


Actually I was probably wrong. "git pull" will see non-ff case and will 
attempt merge of remote and local, unless merge.ff=only is set.


So we can only hope that everyone who has commit rights reads this list 
and will check local clone and do rebase to wipe out this commit if 
necessary. Otherwise it will be resurrected indeed.


May be it's not worse the trouble then to remove it.

___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

Re: [Savannah-users] Anonymous commit (empty Author and Committer)

[Andreas Schwab]

Kaz Kylheku  writes:

> Nope. They will have a git in which that commit looks like their own
> local work. *Someone* will inadvertently do a "git push" to blast out
> their changes based on that deleted commit, thereby causing it to
> reappear.

Not if another one pushes something different in the mean time.

Andreas.

-- 
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

Re: [Savannah-users] Anonymous commit (empty Author and Committer)

[Kaz Kylheku]

On 30.10.2015 13:59, Lennart Sorensen wrote:

I don't have non-fast-forward rights. Does someone from savannah-users
have them? Could he just delete this commit?


If you do that, then anyone that already did a pull after it went in
will have a broken tree.  Rather annoying.


Nope. They will have a git in which that commit looks like their own
local work. *Someone* will inadvertently do a "git push" to blast out
their changes based on that deleted commit, thereby causing it to
reappear.

:)

___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

Re: [Savannah-users] Anonymous commit (empty Author and Committer)

[Andrei Borzenkov]

31.10.2015 10:02, Andreas Schwab пишет:

Kaz Kylheku  writes:


Nope. They will have a git in which that commit looks like their own
local work. *Someone* will inadvertently do a "git push" to blast out
their changes based on that deleted commit, thereby causing it to
reappear.


Not if another one pushes something different in the mean time.



Which is why I said "amended".

___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

Re: [Savannah-users] Anonymous commit (empty Author and Committer)

[André Z . D . A .]

> 30.10.2015 23:59, Lennart Sorensen пишет:
> 
>> On Fri, Oct 30, 2015 at 09:19:19PM +0100, Vladimir 'φ-coder/phcoder' 
>> Serbinenko wrote:
>>
>>> On 30.10.2015 21:09, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>>>
>>>> On 30.10.2015 21:06, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>>>>
>>>>> On 30.10.2015 15:26, Andrei Borzenkov wrote:
>>>>>
>>>>>> See
>>>>>> http://git.savannah.gnu.org/cgit/grub.git/commit/?id=206676601eb853fc319df14cd3398fbdfde665ac
>>>>>>
>>>>>> I was not even aware that this is possible. Is there anything on server
>>>>>> side that can prevent it?
>>>>>>
>>>>>> Would be good if commit were amended and force pushed to fix it.
>>>>>
>>>>> It is a bug in SGit. I'll investigate how it happened
>>>
>>> I don't have non-fast-forward rights. Does someone from savannah-users
>>> have them? Could he just delete this commit?
>>
>> If you do that, then anyone that already did a pull after it went in
>> will have a broken tree. Rather annoying.
> 
> If we decide to fix this commit it is better done now, while it is the
> last one. It is annoying but do you have suggestion how it can be done
> differently?

+1 to undo it now

Indeed. The faster it is fixed smaller the number of potential unintentional 
repeats for it, if any.


___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

Re: [Savannah-users] Anonymous commit (empty Author and Committer)

[Balaco Baco]

> > See 
> > http://git.savannah.gnu.org/cgit/grub.git/commit/?id=206676601eb853fc3
> 19df14cd3398fbdfde665ac
> >
> >
> > 
> > 
> > I was not even aware that this is possible. Is there anything on 
> > server side that can prevent it?
> > 
> > Would be good if commit were amended and force pushed to fix it.
> > 
> > 
> 
> Is this even a problem? I'm pretty sure Git warns you if you try to
> commit something before user.name and user.email are defined, and if
> someone wants to do so, I don't see why you should try to stop them.
> It wouldn't work, anyway; they would just write some simple name like
> "anonymous" and some nonsense email if they really want to be anonymous.
> 

This commit just removed a line from the README:

"Please look at the GRUB Wiki  for
testing-procedures."

Is this change something that may justify that it's-not-me-there action?
I agree that it should not be prevented to avoid some pressure
situations that might be (eventually) present. Bogus random data there
would be harder to track. The empty fields are easy, and if it
guarantees some safety to whoever does it, should be the choice.


-- 
http://www.fastmail.com - mmm... Fastmail...


___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

Re: savannah Browse Sources Repository

[Felix Zielcke]

Am Sonntag, den 29.11.2009, 04:30 +0100 schrieb Robert Millan:
 On Sun, Nov 29, 2009 at 01:49:02AM +, Carles Pina i Estany wrote:
  
  Hello,
  
  From this webpage:
  https://savannah.gnu.org/projects/grub/
  
  Clicking on Browse Sources Repository (Bazaar one) appears:
  http://bzr.savannah.gnu.org/lh/grub
  
  I remember that last Sunday worked fine but not during the week.
 Maybe
  restoring the backup on Sunday after the incorrect merge something
 is
  not working? Or just a coincidence?
 
 Hi,
 
 The web frontend tends to break often.  Anyway, there isn't much we
 can do
 about it.  If you think it's necessary, you could file a problem
 report on
 Savannah admin project.

I already did that but no reply from them :(
https://savannah.gnu.org/support/?107133

-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

savannah Browse Sources Repository

[Carles Pina i Estany]

Hello,

From this webpage:
https://savannah.gnu.org/projects/grub/

Clicking on Browse Sources Repository (Bazaar one) appears:
http://bzr.savannah.gnu.org/lh/grub

I remember that last Sunday worked fine but not during the week. Maybe
restoring the backup on Sunday after the incorrect merge something is
not working? Or just a coincidence?

-- 
Carles Pina i Estany
http://pinux.info


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: savannah Browse Sources Repository

[Robert Millan]

On Sun, Nov 29, 2009 at 01:49:02AM +, Carles Pina i Estany wrote:
 
 Hello,
 
 From this webpage:
 https://savannah.gnu.org/projects/grub/
 
 Clicking on Browse Sources Repository (Bazaar one) appears:
 http://bzr.savannah.gnu.org/lh/grub
 
 I remember that last Sunday worked fine but not during the week. Maybe
 restoring the backup on Sunday after the incorrect merge something is
 not working? Or just a coincidence?

Hi,

The web frontend tends to break often.  Anyway, there isn't much we can do
about it.  If you think it's necessary, you could file a problem report on
Savannah admin project.

-- 
Robert Millan

  The DRM opt-in fallacy: Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all.


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: savannah

[Yoshinori K. Okuji]

On Tuesday 09 August 2005 13:14, Marco Gerards wrote:
 This can be easily implemented in GRUB 2 just like I implemented the
 loopback support.  I did not know how software raid worked in GRUB
 Legacy (I did not know it had software raid support) and I do not know
 if this is the right way to implement it...

GRUB Legacy does not have explicit support, but it works with RAID 1 if you 
install GRUB to /dev/md0, because the disks are just mirroring.

  -lilo -R-like functionality (what's that ? an automatic fallback when
  kernel can't be read ?) to make remote kernel changes safer.

 Something like this is possible with later (the latest?) GRUB Legacy
 release AFAIK/

Yes.

  What comes up is also that most users just keep the default bootloader
  from their distro. And grub seems to be the default bootloader in a
  growing number of distributions.

 Right.  I think it is our task to make GRUB 2 the default. :)

Yes, if your interest is to get many users. I'm not interested very much.

Okuji


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: savannah

[Marco Gerards]

Yoshinori K. Okuji [EMAIL PROTECTED] writes:

 On Tuesday 09 August 2005 13:14, Marco Gerards wrote:
 This can be easily implemented in GRUB 2 just like I implemented the
 loopback support.  I did not know how software raid worked in GRUB
 Legacy (I did not know it had software raid support) and I do not know
 if this is the right way to implement it...

 GRUB Legacy does not have explicit support, but it works with RAID 1 if you 
 install GRUB to /dev/md0, because the disks are just mirroring.

Someone told me that this is not a correct approach.  The correct one
is being able to fall back to the other mirror disk when the first
disk can not be read.  I don't know if this is important or not, I
don't know much about RAID.

  What comes up is also that most users just keep the default bootloader
  from their distro. And grub seems to be the default bootloader in a
  growing number of distributions.

 Right.  I think it is our task to make GRUB 2 the default. :)

 Yes, if your interest is to get many users. I'm not interested very much.

My interest is to make GRUB Legacy obsolete and get more contributors
and testers.

--
Marco



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: savannah

[Marco Gerards]

Yoshinori K. Okuji [EMAIL PROTECTED] writes:

 My interest is to make GRUB Legacy obsolete and get more contributors
 and testers.

 I agree. If you know how to get more developers, please enlighten me.

What I do is talking to people on IRC, to other developers, etc.  But
giving talks helps, so does announcing the release on info-gnu.
Perhaps someone can write a kerneltrap article about GRUB2.  So what
we need is publicity and enthusiastic developers.

--
Marco



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

savannah

[Yoshinori K. Okuji]

Ummh, Savannah seems to be down. Does anybody know why? Was it cracked again?

Okuji


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: savannah

[Vincent Pelletier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Yoshinori K. Okuji wrote:
 And they are still talking about LILO vs. GRUB? Completely off-topic. Who on 
 the earth understands your post? *sigh*

They are asking for a popularity poll between LILO and GRUB.
And they also report some problems they had with grub legacy :
- -software raid (not straightforward with grub)
- -the usual problems with stage 1[.5] not finding stage 2
 (fixed by the grub 2 rescue command line)
- -lilo -R-like functionality (what's that ? an automatic fallback when
kernel can't be read ?) to make remote kernel changes safer.

What comes up is also that most users just keep the default bootloader
from their distro. And grub seems to be the default bootloader in a
growing number of distributions.

Vincent Pelletier
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFC+D3IFEQoKRQyjtURAj4UAJ4kUyc40DUiAxVc0ge9CO+cMp9eBQCbBQR2
XfC+tG2FX2uqsVZZDaFt/ds=
=txlx
-END PGP SIGNATURE-





___ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel