-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Derek Price <[EMAIL PROTECTED]> writes:
> Derek Price wrote:
>
> > |> | So probably the expression used should connote this. After some
> > |> | consideration, I would vote for '.origin' here. I disagree
> > |> with | being meaningless. I often export a project state into a
> > |> local | repository, work on it, and when I'm done, move the files
> > |> back to | the remote repository's sandbox. During local
> > |> development I often | want to compare to the initial version of a
> > |> file, and using a | single tag for this is just easy. Granted
> > |> there are other ways to | achieve this, but they're not as easy
> > |> to handle.
> > |>
> > |> That's fine for 1.1, but how does this help you for a branch?
> > |> You might want to diff against the root, but it doesn't make much
> > |> sense to care about the first revision on the branch.
> > |
> > |
> > | Good point. What about resolving '.origin' to the very first
> > | revision of the mainline?
> >
> >
> > I don't have any reason to object to that.
>
>
> On further consideration, why doesn't -r1.1 suffice for what you want
> to do?
Possibly for handling the following conditions...
- cvs add foo && cvs commit -mnew foo && echo newstuff >>foo \
&& cvs commit -mupdate foo && cvs admin -o1.1 foo
.origin == 1.2 after this operation
- cvs add foo && cvs commit -mnew -r2.1 foo
.origin == 2.1
- cvs tag -b foo-branch && cvs update -rfoo-branch && cvs add foo \
&& cvs commit -mnew foo
In this case, is .origin == 1.1 (dead) or is it not found?
- cvs tag -b foo-branch && cvs update -rfoo-branch && cvs add foo \
&& cvs commit -mnew foo && cvs update -A && cvs up -jfoo-branch \
&& cvs commit -mmerge foo
.origin == 1.2
I have no objections to .origin being used for the very first revision
of the mainline.
-- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCJzbw3x41pRYZE/gRApiNAKC8hOUGy1lvebo27DDnxlXORclf3ACdHabl
CAwLIZj9tAonI7HPZGzhEzM=
=GtfW
-----END PGP SIGNATURE-----
_______________________________________________
Bug-cvs mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-cvs
