From: Theodore Tso <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg KH <gregkh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
pcihpd-discuss@lists.sourceforge.net
Subject: Re: [GIT PATCH] PCI patches for 2.6.24-rc1
Date: Tue, 6 Nov 2007 11:14:06 -0500 [thread overview]
Message-ID: <20071106161406.GD9086@thunk.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0711051414120.15101@woody.linux-foundation.org>
On Mon, Nov 05, 2007 at 02:16:05PM -0800, Linus Torvalds wrote:
>
>
> On Mon, 5 Nov 2007, Linus Torvalds wrote:
> >
> > This one is bogus:
>
> Side note: I pulled and pushed out, since I assume the *code* is correct,
> but please double-check the commit messages for things like this.
>
> gitk makes it really easy, since it will highlight valid commit ID's. It
> looks lik eyou may have re-ordered the commits or something?
hmm, I wonder if it would be a good idea to put together a git hook
script that looks for things that look like git commit ID's, and if
they aren't valid commit ID's that appear in the repository, the
maintainer gets a warning when they do a "git am" or otherwise suck in
a patch that was sent via e-mail...
- Ted
next prev parent reply other threads:[~2007-11-06 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 21:56 Greg KH
2007-11-05 22:13 ` Linus Torvalds
2007-11-05 22:16 ` Linus Torvalds
2007-11-05 22:28 ` Greg KH
2007-11-05 22:42 ` Linus Torvalds
2007-11-05 23:28 ` David Miller
2007-11-06 16:14 ` Theodore Tso [this message]
2007-11-06 16:47 ` Linus Torvalds
2007-11-05 22:17 ` Greg KH
2007-11-05 22:37 ` Linus Torvalds
2007-11-05 23:24 ` David Miller
2007-11-05 23:23 ` David Miller
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=20071106161406.GD9086@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=torvalds@linux-foundation.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®