From: Alex Riesen <raa.lkml@gmail.com>
To: "Mike.lifeguard" <mike.lifeguard@gmail.com>
Cc: Kris Shannon <kris@shannon.id.au>, git@vger.kernel.org
Subject: Re: Pseudonymous commits
Date: Thu, 25 Mar 2010 10:18:51 +0100 [thread overview]
Message-ID: <81b0412b1003250218t3205e12cj5a5013d97e2c0e38@mail.gmail.com> (raw)
In-Reply-To: <4BAAEDF7.1080107@gmail.com>
On Thu, Mar 25, 2010 at 06:00, Mike.lifeguard <mike.lifeguard@gmail.com> wrote:
> In any case, is the answer "git can't do that" or not? Because that's
> actually the answer I'm interested in.
git commit --author "I am not Mike Lifeguard <mike.lifeguard@gmail.com>"
next prev parent reply other threads:[~2010-03-25 9:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 3:57 Pseudonymous commits Mike.lifeguard
2010-03-25 4:39 ` Theodore Tso
2010-03-25 4:41 ` Mike.lifeguard
2010-03-25 4:54 ` Kris Shannon
2010-03-25 5:00 ` Mike.lifeguard
2010-03-25 5:14 ` Avery Pennarun
2010-03-25 9:18 ` Alex Riesen [this message]
2010-03-25 11:05 ` Santi Béjar
2010-03-25 19:02 ` Nicolas Pitre
2010-03-25 19:26 ` Mike.lifeguard
2010-03-25 20:14 ` Nicolas Pitre
2010-03-25 21:30 ` Chris Packham
2010-03-25 23:57 ` Jakub Narebski
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=81b0412b1003250218t3205e12cj5a5013d97e2c0e38@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=kris@shannon.id.au \
--cc=mike.lifeguard@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).