Ahh, the cobite.com address worked ;)
David, as you may or may not be aware, the dm.cobite.com address was
bouncing at least as of yesterday.
On Tue, 26 Jul 2005, David Mansfield wrote:
>
> It 'smells' wierd to have to revisions in the same patchset at all, but
> I suppose you've all been through that before.
It seems to be just a result of how BK ends up having this internal notion
of a "delta", and one commit can contain multiple deltas to the same file.
That's really just some BK internal implementation issue showing through -
the deltas really aren't even individually accessible, it's just that BK
has this two-stage commit thing where you first commit the individual file
changes (the "delta") and then you do the _real_ commit which gathers them
all up.
Normally you don't even see this at all, since the tools basically hide
this, but especially if you script things you'll see the difference.
In fact, in many ways the usage model when scripting ends up being a bit
like the git two-phase "git-update-cache" + "git commit" approach,
although for totally different reasons. But unlike git, you can actually
tell how somebody did several updates on the same file, and it seems to
show through in the bkcvs archives.
I bet that it wasn't even intentional, and that it's really just a result
of the bkcvs thing really just being pretty much a raw SCCS->RCS
translation (with the addition of the "changeset" notion at a higher
level).
So normally you'd not like to see this unless you use the --bkcvs flag,
but I suspect that with a big fuzz-factor and repeated commit messages you
can see it even with a perfectly normal CVS tree - if only because cvsps
might collapse two separate commits that shouldn't really be collapsed.
Linus
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
