git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Balaco Baco <balacobaco@imap.cc>
To: The development of GRUB 2 <grub-devel@gnu.org>,
	git@vger.kernel.org, savannah-users@gnu.org
Subject: Re: [Savannah-users] Anonymous commit (empty Author and Committer)
Date: Fri, 30 Oct 2015 12:39:42 -0300	[thread overview]
Message-ID: <1446219582.3019364.424715177.39046D65@webmail.messagingengine.com> (raw)
In-Reply-To: <56338C30.6010302@riseup.net>


> > 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 <http://grub.enbug.org> 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...

  parent reply	other threads:[~2015-10-30 15:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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   ` Balaco Baco [this message]
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:37             ` [Savannah-users] " Kaz Kylheku
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=1446219582.3019364.424715177.39046D65@webmail.messagingengine.com \
    --to=balacobaco@imap.cc \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).