From: Christoph Hellwig <hch@infradead.org>
To: Larry McVoy <lm@work.bitmover.com>,
Christoph Hellwig <hch@infradead.org>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] push down inclusion of buffer_head.h into users
Date: Tue, 21 May 2002 09:12:03 +0100 [thread overview]
Message-ID: <20020521091203.A6252@infradead.org> (raw)
In-Reply-To: <20020520190033.A414@infradead.org> <20020521011108.A22488@infradead.org> <20020520181731.K2996@work.bitmover.com>
On Mon, May 20, 2002 at 06:17:31PM -0700, Larry McVoy wrote:
> Hi Christoph,
>
> while it is true that BK will do the right thing if Linus applies this patch
> and then you pull it, it's a lot nicer if you let him pull your tree.
Who sais that I actually have a checked in BK tree of it? For all one-time
patches I just edit a checked out BK tree, crate an unified diff using
bk diffs -u and then clean all modified files using a small script.
prev parent reply other threads:[~2002-05-21 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 18:00 [PATCH] push down inclusion of buffer_head.h into users Christoph Hellwig
2002-05-21 0:11 ` Christoph Hellwig
2002-05-21 1:17 ` Larry McVoy
2002-05-21 8:12 ` Christoph Hellwig [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=20020521091203.A6252@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@work.bitmover.com \
--cc=torvalds@transmeta.com \
/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