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.
next reply other threads:[~2015-10-31 12:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-31 12:12 André Z. D. A. [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-30 14:26 Anonymous commit (empty Author and Committer) Andrei Borzenkov
2015-10-30 14:33 ` Konstantin Khomoutov
2015-10-30 17:01 ` Jeff King
[not found] ` <5633CDCD.10004@gmail.com>
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 ` Kaz Kylheku
2015-10-31 7:02 ` Andreas Schwab
2015-10-31 13:46 ` Andrei Borzenkov
2015-10-31 5:24 ` Andrei Borzenkov
2015-11-02 15:11 ` Lennart Sorensen
2015-11-02 16:42 ` Junio C Hamano
2015-10-31 13:54 ` Andrei Borzenkov
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$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=grub-devel@gnu$(echo .)org \
--cc=savannah-users@gnu$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox