From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] PCI patches for 2.6.16-rc1
Date: Tue, 31 Jan 2006 23:21:38 -0800 [thread overview]
Message-ID: <7v8xsvk0hp.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0601312016370.7301@g5.osdl.org> (Linus Torvalds's message of "Tue, 31 Jan 2006 20:19:55 -0800 (PST)")
Linus Torvalds <torvalds@osdl.org> writes:
> Btw, Linas - even if you can't fix your broken mail setup, what you _can_
> do is to always make sure that the patches you send out have
>
> From: Linas Vepstas <linas@austin.ibm.com>
>
> as the first line of the body - then the tools will figure out to use that
> instead of the broken mail headers. Ok?
BTW, Linus - even if Linas did you already have commits with
broken author information; what you _can_ do is to have the
following entry in a .mailmap file in your linux-2.6.git
repository, where you run git-shortlog for your next
announcement:
$ cat .mailmap
Linas Vepstas <linas@austin.ibm.com>
Linus Torvalds <torvalds@osdl.org>
...
$
Then the tool will pick up Author: line of the commit (which
is {'linas', '<linas@austin.ibm.com>'} pair) and figure out to
use the canonical "name" you define there instead of the broken
commit headers. OK?
> (This is true in general - so anybody else who knows that they send out
> emails from a strange address that they'd rather have show up as their
> "real" email address instead in the changelogs can do the same).
(This is also true in general - so any upstream maintainer who
ended up with commits that have badly formatted author
information in his repository that they'd rather have show up
nicer in the changelogs can do the same).
> Linus
Junio ;-).
next prev parent reply other threads:[~2006-02-01 7:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 2:04 Greg KH
2006-02-01 2:16 ` Linus Torvalds
2006-02-01 4:03 ` Greg KH
2006-02-01 4:19 ` Linus Torvalds
2006-02-01 7:21 ` Junio C Hamano [this message]
2006-02-01 22:20 ` Linas Vepstas
2006-02-01 22:39 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2006-01-20 19:04 Greg KH
2006-01-20 19:23 ` Greg KH
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=7v8xsvk0hp.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®