From: Roland Dreier <rdreier@cisco.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, axboe@kernel.dk
Subject: Re: [git pull] bdev API series
Date: Thu, 23 Oct 2008 14:40:08 -0700 [thread overview]
Message-ID: <adazlkvrnwn.fsf@cisco.com> (raw)
In-Reply-To: <20081023100124.GK28946@ZenIV.linux.org.uk> (Al Viro's message of "Thu, 23 Oct 2008 11:01:24 +0100")
I think it would be worth trying to get the patch descriptions a little
better for future trees at least -- if I'm reading through a shortlog or
something and I see:
> switch ubd
> switch DAC960
> switch amiflop
> switch aoeblk
> switch ataflop
then it's not exactly clear what those patches do (without the context
of the full series handy).
- R.
prev parent reply other threads:[~2008-10-23 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 10:01 [git pull] bdev API series Al Viro
2008-10-23 21:40 ` Roland Dreier [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=adazlkvrnwn.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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