All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Fw: [PATCH 31/49] PCI: PCI/Cardbus cards hidden, needs pci=assign-busses to fix
Date: Thu, 23 Mar 2006 22:17:06 -0800	[thread overview]
Message-ID: <20060324061706.GA11248@kroah.com> (raw)
In-Reply-To: <7v3bh837cs.fsf@assigned-by-dhcp.cox.net>

On Thu, Mar 23, 2006 at 06:27:15PM -0800, Junio C Hamano wrote:
> Andrew Morton <akpm@osdl.org> writes:
> 
> > We wouldn't want to attempt to mix this concept up with email envelopes or
> > email headers or anything like that.  The authorship is an attribute of the
> > patch, and has nothing to do with how it was transported, stored or
> > anything like that.
> 
> Fair enough.  This is the approach I called "the second best" in
> my message but I am inclined to agree with you.
> 
> This was tested once by sending myself two patches.

Oops, just saw this after I sent out the last set of patches.  It looks
good to me, I'll try it out next time.

And yes, I did write the original version of this perl script, but it's
been fixed up and made useful by Ryan.

thanks,

greg k-h

  reply	other threads:[~2006-03-24  6:19 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     ` Fw: [PATCH 31/49] PCI: PCI/Cardbus cards hidden, needs pci=assign-busses to fix Greg KH
2006-03-24  0:55       ` 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 [this message]
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=20060324061706.GA11248@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.