From: Sam Ravnborg <sam@ravnborg.org>
To: Jochen Friedrich <jochen@scram.de>
Cc: Matthias Andree <matthias.andree@gmx.de>,
Linux-Kernel mailing list <linux-kernel@vger.kernel.org>,
Andreas Dilger <adilger@turbolabs.com>,
Larry McVoy <lm@bitmover.com>
Subject: Re: Documentation/BK-usage/bksend problems?
Date: Sun, 5 Jan 2003 08:58:42 +0100 [thread overview]
Message-ID: <20030105075842.GA1256@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0301050839340.19683-100000@gfrw1044.bocc.de>
On Sun, Jan 05, 2003 at 08:42:59AM +0100, Jochen Friedrich wrote:
> Hi Matthias,
>
> > The changes are fine, for 1.838 and 1.839, but the patch itself only
> > contains the effects of 1.839. The attached gzip_uu wrapped bk
> > "receive"able stuff is fine again and contains both ChangeSets.
> >
> > It seems as though it would take "diff 1.839 against 1.838" for bk gnupatch
> > and "changesets 1.838 to 1.839 inclusively" for bk send.
>
> I noticed the same when sending my Token Ring updates. Here i tried to
> send 4 changesets and only the second one ended up in the patch while the
> bk send part was OK. This was on Alpha, so i don't think it's arch
> dependent.
I have seen something similar.
bk export -tpatch -r1.984..1.985
only exports cset 1.985
bk export -tpatch -r1.984
exports cset 1.984 as expected.
bk export -tpatch -r1.983..1.985
will export cset 1.984+1.985.
BK Version:
BitKeeper version is bk-3.0 20021011025136 for x86-glibc22-linux
Built by: lm@redhat71.bitmover.com in /build/bk-3.0-lm/src
Built on: Thu Oct 10 20:33:13 PDT 2002
I will submit this with bk sendbug now.
Sam
next prev parent reply other threads:[~2003-01-05 7:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 1:54 Documentation/BK-usage/bksend problems? Matthias Andree
2003-01-05 7:42 ` Jochen Friedrich
2003-01-05 7:58 ` Sam Ravnborg [this message]
2003-01-05 12:00 ` Matthias Andree
2003-01-05 14:55 ` Larry McVoy
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=20030105075842.GA1256@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=adilger@turbolabs.com \
--cc=jochen@scram.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=matthias.andree@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.