Re: CVS: versioning and branching
will guaraldi <[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.devel |
|---|---|
| Message-ID | <[email protected]> |
On Tue, 29 Mar 2005, Steven Armstrong wrote:
>
> If nobody has any objections I'ld like to tag the current CVS state as
> version 1.2. This would give us the possbility to develop towards 1.3 in
> CVS HEAD, while still having the chance to go back and create a branch
> based on v1.2 to fix any urgent bugs/issues that may come up with the
> current release.
>
> What do you think?
I think it's a great idea. My CVS guru-level is like 0, though, which is
why I haven't futzed with branches, versions, and the like. It's one of
those things in a long list of things I really want to learn/use, but
haven't gotten around to yet.
So, after you've done whatever it is you're doing, if you could do a quick
write-up on how to switch between HEAD and other versions and whether
there are any other process changes beyond the whole:
cvs update -dP
... do some stuff ...
cvs commit filex
I'd really appreciate it. It doesn't have to be anything fancy. Mostly
my issue is that I don't know what the various cvs command switches that
would be needed do.
/will
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click