git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Erik Faye-Lund <kusmabite@gmail.com>
Cc: "J. Bakshi" <joydeep@infoservices.in>,
	"Carlos Martín Nieto" <cmn@elego.de>,
	"Ævar Arnfjörð" <avarab@gmail.com>,
	git@vger.kernel.org
Subject: Re: How to force git to use authentication as author
Date: Thu, 14 Jul 2011 14:45:52 -0500	[thread overview]
Message-ID: <20110714194552.GA14632@elie> (raw)
In-Reply-To: <CABPQNSY3qyQXO4hyM6xhHq2VYhK5369ihuqJ5PDAonN7+UpcGA@mail.gmail.com>

Hi,

Erik Faye-Lund wrote:

> So let's step back a little bit. Why do you want the author to be
> identical to the authenticated user in the first place? Is it to be
> able to *prove* (i.e not trust the users that push) who wrote what
> code? If so, let's me first tell you that giving someone push-access
> while not trusting them is a bit crazy. But if you're happy with being
> a bit crazy, you'd might want to somehow cryptographically sign the
> commits instead. I'd go for PGP-signing the patch-id, and putting that
> in a git-note.

Let's suppose you want to be able to decide who was to blame for the
latest breakage, not on a per-commit level but on a per-push level.
Then that seems quite doable to me through simpler means, on the
server side.  See

 http://sitaramc.github.com/gitolite/doc/3-faq-tips-etc.html#_better_logging

Hope that helps.
Jonathan

      reply	other threads:[~2011-07-14 19:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-14 10:36 How to force git to use authentication as author J. Bakshi
2011-07-14 10:38 ` Ævar Arnfjörð Bjarmason
2011-07-14 10:48   ` J. Bakshi
2011-07-14 11:00     ` Carlos Martín Nieto
2011-07-14 11:15       ` J. Bakshi
2011-07-14 11:38         ` Carlos Martín Nieto
2011-07-14 12:00           ` Erik Faye-Lund
2011-07-14 12:19             ` J. Bakshi
2011-07-14 12:26               ` Carlos Martín Nieto
2011-07-14 12:01           ` J. Bakshi
2011-07-14 12:16             ` Ferry Huberts
2011-07-14 12:44           ` Jakub Narebski
2011-07-14 11:38         ` J. Bakshi
2011-07-14 11:53         ` Erik Faye-Lund
2011-07-14 19:45           ` Jonathan Nieder [this message]

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=20110714194552.GA14632@elie \
    --to=jrnieder@gmail.com \
    --cc=avarab@gmail.com \
    --cc=cmn@elego.de \
    --cc=git@vger.kernel.org \
    --cc=joydeep@infoservices.in \
    --cc=kusmabite@gmail.com \
    /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).