From: Larry McVoy <lm@bitmover.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Hans Reiser <reiser@namesys.com>, linux-kernel@vger.kernel.org
Subject: Re: ReiserFS Bug Fixes 3 of 6 (Please apply all 6)
Date: Fri, 5 Apr 2002 17:10:01 -0800 [thread overview]
Message-ID: <20020405171001.C6087@work.bitmover.com> (raw)
In-Reply-To: <200204052027.g35KRc002869@bitshadow.namesys.com> <Pine.LNX.4.33.0204051347500.1746-100000@penguin.transmeta.com>
On Fri, Apr 05, 2002 at 01:48:30PM -0800, Linus Torvalds wrote:
>
> On Sat, 6 Apr 2002, Hans Reiser wrote:
> >
> > This changeset is to fix several reiserfs problems which can be
> > fixed in non-intrusive way.
>
> Please don't use bk patches, they have turned out to be pretty much
> unusable.
I suspect that the problem is that BK won't let you accept a patch unless
the receiving repository has the parent of the patch. In other words,
this won't work:
bk clone bk://linux.bkbits.net/linux-2.5
<make some changes>
bk commit (or bk citool) # creates changeset 1.800
<make some changes>
bk commit (or bk citool) # creates changeset 1.801
# Now you want to send the second patch to Linus so you do a:
bk send -r+ - | mail linux-kernel@vger.kernel.org
That will fail when Linus tries to accept the patch, because he doesn't
have your 1.800.
The easiest thing is to do what he suggests:
> Either make a (controlled) bk tree available for pulling, or just use
> old-fashioned patches.
and if you want to go the "tree for pulling", you can either point him at
a BK url you maintain, or you are welcome to go grab resierfs.bkbits.net
and stash it there. See http://www.bitkeeper.com/Hosted.html for information
on how to set up a project here.
At some point, we'll package up the whole bkbits.net infrastructure as an
installable RPM (not the project data, the infrastructure), and you'll be
able to do this at resierfs.bkbits.kernel.org or something like that, but
right now we're just too overworked to do so.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-04-06 1:10 UTC|newest]
Thread overview: 13+ 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 [this message]
2002-04-06 12:00 ` Hans Reiser
2002-04-06 17:01 ` Larry McVoy
2002-04-06 18:11 ` [reiserfs-dev] " Oleg Drokin
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
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 21:18 Torrey Hoffman
2002-04-10 21:28 ` Florian Weimer
2002-04-13 20:03 ` Alan Cox
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=20020405171001.C6087@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.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