From: Oleg Drokin <green@namesys.com>
To: Larry McVoy <lm@work.bitmover.com>,
Hans Reiser <reiser@namesys.com>, Larry McVoy <lm@bitmover.com>,
reiserfs-dev@namesys.com, linux-kernel@vger.kernel.org,
flx <flx@namesys.com>
Subject: Re: [reiserfs-dev] Re: ReiserFS Bug Fixes 3 of 6 (Please apply all 6)
Date: Sat, 6 Apr 2002 22:11:50 +0400 [thread overview]
Message-ID: <20020406221150.A9754@namesys.com> (raw)
In-Reply-To: <200204052027.g35KRc002869@bitshadow.namesys.com> <Pine.LNX.4.33.0204051347500.1746-100000@penguin.transmeta.com> <20020405171001.C6087@work.bitmover.com> <3CAEE365.4020301@namesys.com> <20020406090157.A12017@work.bitmover.com>
Hello!
On Sat, Apr 06, 2002 at 09:01:57AM -0800, Larry McVoy wrote:
> > I am confused, the bk patches look like they have normal patches at the
> > top of them.
> If you just want to send him regular patches, use bk export -tpatch.
> That's sort of a lame way to go if you are using BK on both ends,
> you're going to end up merging your changes with your changes when
> you pull from Linus' tree. There are lots of reasons why this isn't
> a good idea.
In fact, per one of the original 'BK Patches sending' HOWTO,
we are including output of bk export -tpatch ... stuff prior to
bk send ... - stuff.
So that people who want to get the diff, can get it without silly tricks.
Bye,
Oleg
next prev parent reply other threads:[~2002-04-06 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 20:27 ReiserFS Bug Fixes 3 of 6 (Please apply all 6) Hans Reiser
2002-04-05 21:48 ` Linus Torvalds
2002-04-06 1:10 ` Larry McVoy
2002-04-06 12:00 ` Hans Reiser
2002-04-06 17:01 ` Larry McVoy
2002-04-06 18:11 ` Oleg Drokin [this message]
2002-04-07 10:04 ` Hans Reiser
2002-04-10 19:21 ` Florian Weimer
2002-04-10 19:34 ` James Simmons
2002-04-10 19:55 ` Florian Weimer
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=20020406221150.A9754@namesys.com \
--to=green@namesys.com \
--cc=flx@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=lm@work.bitmover.com \
--cc=reiser@namesys.com \
--cc=reiserfs-dev@namesys.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