From: Greg KH <greg@kroah.com>
To: Grant Coady <grant_lkml@dodo.com.au>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3 04a/04] pci_ids: whitespace cleanup, resend first half
Date: Thu, 29 Sep 2005 09:14:51 -0700 [thread overview]
Message-ID: <20050929161450.GC19770@kroah.com> (raw)
In-Reply-To: <vo0nj19p336vsm05mrtefan1fajgi6qngi@4ax.com>
On Thu, Sep 29, 2005 at 04:02:26PM +1000, Grant Coady wrote:
>
> From: Grant Coady <gcoady@gmail.com>
>
> pci_ids.h: whitespace cleanup, split into two 'cos lkml ate single patch.
This patch is going to be tough, as it will conflict with everything at
the same time (other trees that touch the file.)
I'll do this by hand, right before sending Linus a PCI git tree to
merge, if you don't mind.
> + *
> + * September 2005 - cleanup by Grant Coady <gcoady@gmail.com>
changelog stuff within files is not needed, or encouraged at all.
That's why we have changelogs now.
thanks,
greg k-h
next prev parent reply other threads:[~2005-09-29 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 6:02 [PATCHv3 04a/04] pci_ids: whitespace cleanup, resend first half Grant Coady
2005-09-29 16:14 ` Greg KH [this message]
2005-09-29 19:29 ` Grant Coady
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=20050929161450.GC19770@kroah.com \
--to=greg@kroah.com \
--cc=grant_lkml@dodo.com.au \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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