From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: savannah-users@gnu.org, git@vger.kernel.org
Subject: Anonymous commit (empty Author and Committer)
Date: Fri, 30 Oct 2015 17:26:00 +0300 [thread overview]
Message-ID: <56337DF8.5050802@gmail.com> (raw)
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.
WARNING: multiple messages have this Message-ID (diff)
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: git@vger.kernel.org, savannah-users@gnu.org
Subject: Anonymous commit (empty Author and Committer)
Date: Fri, 30 Oct 2015 17:26:00 +0300 [thread overview]
Message-ID: <56337DF8.5050802@gmail.com> (raw)
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.
next reply other threads:[~2015-10-30 14:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 14:26 Andrei Borzenkov [this message]
2015-10-30 14:26 ` Anonymous commit (empty Author and Committer) Andrei Borzenkov
2015-10-30 14:33 ` Konstantin Khomoutov
[not found] ` <56338C30.6010302@riseup.net>
2015-10-30 15:39 ` [Savannah-users] " Balaco Baco
2015-10-30 17:01 ` Jeff King
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:19 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-10-30 20:59 ` Lennart Sorensen
2015-10-30 20:59 ` Lennart Sorensen
2015-10-30 21:45 ` [Savannah-users] " Kaz Kylheku
2015-10-30 21:45 ` Kaz Kylheku
2015-10-31 7:02 ` [Savannah-users] " Andreas Schwab
2015-10-31 7:02 ` Andreas Schwab
2015-10-31 13:46 ` [Savannah-users] " Andrei Borzenkov
2015-10-31 13:46 ` Andrei Borzenkov
2015-11-03 3:59 ` [Savannah-users] " 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
2015-11-02 16:42 ` Junio C Hamano
2015-11-02 16:42 ` Junio C Hamano
2015-10-31 13:54 ` Andrei Borzenkov
2015-11-02 7:24 ` Vladimir 'phcoder' Serbinenko
2015-10-30 22:07 ` Vladimir 'phcoder' Serbinenko
-- strict thread matches above, loose matches on Subject: below --
2015-10-31 12:12 André Z. D. A.
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=56337DF8.5050802@gmail.com \
--to=arvidjaar@gmail.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.