From: Ingo Oeser <ioe-lkml@rameria.de>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] final PCI patches for 2.6.26
Date: Sun, 15 Jun 2008 00:15:33 +0200 [thread overview]
Message-ID: <200806150015.33758.ioe-lkml@rameria.de> (raw)
In-Reply-To: <200806121519.24194.jbarnes@virtuousgeek.org>
Hi Jesse,
On Friday 13 June 2008, Jesse Barnes wrote:
> Right, I probably should have used one of the git mail scripts... but this
> wasn't a real git pull request either, more of a "hey please sanity check
> this" type thing. I figured in this case keeping the changelogs was
> important, but didn't want to spam people with a bunch of messages when the
> total size really wasn't that big...
A bunch of THREADED messages are quite easy to skip (single keystroke for me).
So just use one of those git mail scripts, which can do threading
and everyone is happy.
Best Regards
Ingo Oeser, wading through lkml since >10 years.
prev parent reply other threads:[~2008-06-14 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 20:34 Jesse Barnes
2008-06-12 21:45 ` Jeff Garzik
2008-06-12 22:19 ` Jesse Barnes
2008-06-14 22:15 ` Ingo Oeser [this message]
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=200806150015.33758.ioe-lkml@rameria.de \
--to=ioe-lkml@rameria.de \
--cc=jbarnes@virtuousgeek.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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
all inboxes | Powered by JetHome®