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

On 02.11.2015 07:11, Lennart Sorensen wrote: On Sat, Oct 31, 2015 at 08:24:06AM +0300, Andrei Borzenkov wrote: 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? Well the only options are:

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

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

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

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.

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

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

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

> > 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