From: Jens Axboe <axboe@suse.de>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block: Documentation/block/barrier.txt got lost, add it back
Date: Mon, 16 Jan 2006 09:44:29 +0100 [thread overview]
Message-ID: <20060116084428.GP3945@suse.de> (raw)
In-Reply-To: <11372222783378-git-send-email-htejun@gmail.com>
On Sat, Jan 14 2006, Tejun Heo wrote:
> barrier.txt got lost while the new barrier patchset was climbing up
> the ladder to the mainline. Add it back.
Must have been a missing git-update-index --add, thanks I've queued it
up for Linus.
--
Jens Axboe
prev parent reply other threads:[~2006-01-16 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 7:04 [PATCH] block: Documentation/block/barrier.txt got lost, add it back Tejun Heo
2006-01-16 8:44 ` Jens Axboe [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=20060116084428.GP3945@suse.de \
--to=axboe@suse.de \
--cc=htejun@gmail.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