Dnia pi± 2. kwietnia 2004 22:44, John Peacock napisa³:
> Marcin Kasperski wrote:
> > I were working in subversion would never exist so. Take the
> > following scenario (we are editing some module):
> > - I edit file blahblah.cxx and commit
> > - I edit file trahtrah.cxx and commit
> > - I add one more change to blahblah.cxx and commit
> > - I decide that I need to distribute the version containing
> > current blahblah.cxx but without the last change in
> > trahtrah.cxx (say, it occured that I can not finish the
> > change in trahtrah before release date)
> >
> > In subversion it is not easy to mark such a version.
>
> It's not that hard, either. Copy the project as it existed
> before the change to trahtrah.cxx (copies are cheap). Then
> switch to that branch and merge in the second change to
> blahblah.cxx and commit. Voila, you now have a version with
> the files in the state you desired. You can treat this as a
> tag by moving the branch to a tag folder, or you can make the
> original copy in the tag folder (since tags are a convention
> not a restriction).
CVS version of solving this case seems to be far easier for me:
- cvs tag mynewtag
- cs log trahtrah.cxx # To check which revision I need
- cvs tag -F -r1.343 trahtrah.cxx
No branches, no merges. I just label what I need and go.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 2 22:54:17 2004