From: Jens Axboe <axboe@suse.de>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] queue barrier support
Date: Wed, 13 Feb 2002 16:18:38 +0100 [thread overview]
Message-ID: <20020213161838.P1907@suse.de> (raw)
In-Reply-To: <20020213135134.A1907@suse.de> <E16b0l7-0001nn-00@starship.berlin>
In-Reply-To: <E16b0l7-0001nn-00@starship.berlin>
On Wed, Feb 13 2002, Daniel Phillips wrote:
> On February 13, 2002 01:51 pm, Jens Axboe wrote:
> > Patches attached, comments welcome.
>
> A meta-comment: the BK url's are wonderfully informative and useful, but they
> are long and _ugly_! Is there anything that can be done about that?
Yeah I like them too, maybe if I just figured out how to get BitKeeper
to dump full changeset info I could just inline them in the mail
instead. I'll look at up and try that next time.
--
Jens Axboe
next prev parent reply other threads:[~2002-02-13 15:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 12:51 [PATCH] queue barrier support Jens Axboe
2002-02-13 13:09 ` Martin Dalecki
2002-02-13 13:13 ` Jens Axboe
2002-02-13 14:36 ` Martin Dalecki
2002-02-13 14:41 ` Jens Axboe
2002-02-13 14:51 ` Daniel Phillips
2002-02-13 15:18 ` Jens Axboe [this message]
2002-02-13 17:47 ` Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2002-02-13 18:26 James Bottomley
2002-02-15 9:02 ` Jens Axboe
2002-02-15 15:15 ` James Bottomley
2002-02-15 16:28 ` Chris Mason
2002-02-15 16:51 ` James Bottomley
2002-02-15 17:17 ` Chris Mason
2002-02-15 17:48 ` James Bottomley
2002-02-15 22:30 ` Matthias Andree
2002-02-15 17:09 ` James Bottomley
2002-02-15 16:43 ` Mike Anderson
2002-02-15 13:41 ` Chris Mason
2002-02-16 10:20 ` Daniel Phillips
2002-02-16 15:02 ` James Bottomley
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=20020213161838.P1907@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox