![]() | |||||||||||||
Messages in this thread |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 12:32 [from the cache] ©2003-2008 | |||||||||||||