From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: Fw: [PATCH 31/49] PCI: PCI/Cardbus cards hidden, needs pci=assign-busses to fix
Date: Thu, 23 Mar 2006 16:46:54 -0800 [thread overview]
Message-ID: <20060324004654.GA19763@kroah.com> (raw)
In-Reply-To: <20060323163844.5fda7589.akpm@osdl.org>
On Thu, Mar 23, 2006 at 04:38:44PM -0800, Andrew Morton wrote:
>
> (added Junio)
Added the git mailing list as everyone should get involved :)
> recap: the patch emails which Greg sends to linux-kernel do not identify
> their actual Author.
>
>
> Greg KH <greg@kroah.com> wrote:
> >
> > On Thu, Mar 23, 2006 at 04:15:21PM -0800, Andrew Morton wrote:
> > >
> > > It's unclear from this email who the patch author was?
> >
> > Git seems to strip that off when it converts them to emails. It was:
> > From: Bernhard Kaindl <bk@suse.de>
> >
> > If you look at the git changeset, it got it correct.
> >
>
> OK. We really should have a
>
> From: Bernhard Kaindl <bk@suse.de>
>
> right at the start of the email, IMO. Can you describe how you're producing
> them please?
I'm using:
git format-patch -n origin..HEAD
to generate the raw patch files, and then:
git-send-email --in-reply-to "<some_message_id>" --to some_mailing_list@somewhere.com
fixing the obvious message id and mailing list address to be the correct
one depending on the subsystem the patches are from.
thanks,
greg k-h
next parent reply other threads:[~2006-03-24 0:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060323161521.28a874e6.akpm@osdl.org>
[not found] ` <20060324002930.GA21184@kroah.com>
[not found] ` <20060323163844.5fda7589.akpm@osdl.org>
2006-03-24 0:46 ` Greg KH [this message]
2006-03-24 0:55 ` Fw: [PATCH 31/49] PCI: PCI/Cardbus cards hidden, needs pci=assign-busses to fix Greg KH
2006-03-24 1:26 ` Junio C Hamano
2006-03-24 1:51 ` Andrew Morton
2006-03-24 2:27 ` Junio C Hamano
2006-03-24 6:17 ` Greg KH
2006-03-24 7:44 ` Junio C Hamano
2006-03-24 17:23 ` Ryan Anderson
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=20060324004654.GA19763@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).