All of lore.kernel.org
 help / color / mirror / Atom feed
From: "André Z. D. A." <andrezda10@yandex.com>
To: savannah-users@gnu.org, git@vger.kernel.org,
	The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [Savannah-users] Anonymous commit (empty Author and Committer)
Date: Sat, 31 Oct 2015 10:12:10 -0200	[thread overview]
Message-ID: <863961446293530@web5m.yandex.ru> (raw)

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



WARNING: multiple messages have this Message-ID (diff)
From: "André Z. D. A." <andrezda10@yandex.com>
To: savannah-users@gnu.org, git@vger.kernel.org,
	The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Anonymous commit (empty Author and Committer)
Date: Sat, 31 Oct 2015 10:12:10 -0200	[thread overview]
Message-ID: <863961446293530@web5m.yandex.ru> (raw)

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

             reply	other threads:[~2015-10-31 13:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-31 12:12 André Z. D. A. [this message]
2015-10-31 12:12 ` Anonymous commit (empty Author and Committer) André Z. D. A.
  -- strict thread matches above, loose matches on Subject: below --
2015-10-30 14:26 Andrei Borzenkov
     [not found] ` <56338C30.6010302@riseup.net>
2015-10-30 15:39   ` [Savannah-users] " Balaco Baco
2015-10-30 20:06 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-10-30 20:09   ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-10-30 20:19     ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-10-30 20:59       ` Lennart Sorensen
2015-10-30 21:45         ` [Savannah-users] " Kaz Kylheku
2015-10-31  7:02           ` Andreas Schwab
2015-10-31 13:46             ` Andrei Borzenkov
2015-11-03  3:59               ` Andrei Borzenkov
2015-11-06 10:43                 ` Vladimir 'phcoder' Serbinenko
2015-10-31  5:24         ` Andrei Borzenkov
2015-11-02 15:11           ` Lennart Sorensen
2015-11-02 16:37             ` [Savannah-users] " Kaz Kylheku
2015-11-02 16:37               ` Kaz Kylheku

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=863961446293530@web5m.yandex.ru \
    --to=andrezda10@yandex.com \
    --cc=git@vger.kernel.org \
    --cc=grub-devel@gnu.org \
    --cc=savannah-users@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.