>
>1.6 AFTER_OOPS (same as RELEASE)
>1.5 BETA3 / OOPS
>1.4 BETA2
>1.3.2.1 (really no tag, but same as 1.5)
>1.3 RELEASE / BETA_branch (the take would really be on this ver)
>1.2 preREL
>1.1 start
>
>You lose nothing.
>You still have your history of check ins (very important).
>You can still do co -r BETA2 and get what you mean. Same with BETA3.
>That's what's important
It seems like the history of this file has been somewhat lost or at least
obscured. How does one note for future reference that 1.4 is part of the
1.3.2 branch and comes before 1.3.2.1?
I guess you could put that info in the log message when the branch is
committed and then modify the log message for 1.4 too.
But I agree with you that the most important information and the capability
to recover it is still there and that a perl script to make it all better
would be more trouble then its worth.
Thanks for your help,
Rob
[EMAIL PROTECTED]
