On Tue, Jun 17, 2003 at 03:02:36PM -0500, kfogel@collab.net wrote:
> But in the VCP code, I couldn't find the logic that a) decides which
> revision to do the initial copy from and b) compensates for any
> "wrong" material accidentally included by copying that revision. Such
> material can arise, for example, when a branch was created on a set of
> files/cvsrevs that were never all in HEAD at the same time in CVS. In
> this situation, copying a single Subversion will wrongly include some
> files/revs that aren't on the branch, and these would have to be
> adjusted before the revision is committed (either by recopying from
> elsewhere, or deleting).
for a), VCP core deduces per-file placeholder rev at the branching
point. my VCP::Dest::svn::create_branch makes use of them and deduces
the `cp point' from those placeholder revisions.
for b), that's the case i mentioned the current branch point guessing
is aggressive, and i need to do more strict checks.
let me make sure if the following is producing the case you meant:
cvs add file1 file2
<some modification and commits>
cvs tag -b somebranch
cvs add file3
<manually edit file3,v to have the time ealier than the branching time>
> I understand that the sympa/ repository may not have any such cases.
> That's why I went looking in the VCP svn driver code itself, and then
> elsewhere in VCP. The fact that I didn't find the logic I expected
> might not mean anything. Perhaps VCP solves this problem in some way
> I wasn't expecting -- that would be nice, in fact :-).
in the current svn implmentation, the easiest way to do so is to
compare the placeholder revs and the copied files in branch showed
by svn up after the svn cp. but it'd be harder to do so if i switch
to svndumpfile, since i need to keep more states about directories.
Cheers,
CLK
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 18 05:51:23 2003