[EMAIL PROTECTED] wrote:
Something I do frequently is push small changes from a dev site to a
live site. In CVS I do this by tagging the files in the dev site I
want to move over with "stable", then going over to the live site
(which was originally created by checking out on the "stable" tag) and
doing a "cvs update". Voila.
I asked on the Subversion list how this same action would be
accomplished, since they don't have tags in the CVS sense. I received
several replies, which boiled down to this: create a tag, which is
really just a 'cheap copy' of the current state of the repository,
called /tags/stable (the /tags directory is optional, but is a
convention they recommend).
I think you're somewhat missing the boat here. In CVS, there is no way
to group a set of changes. Every commit stands alone. In subversion
you can commit as many files as you like in one operation and you get 1
revision. Yesterday I svn committed 20-some odd files and got to
revision 73 of my codebase. All of them needed to be changed together
to support 1 enhancement (darn J2EE). I _know_ which set of files
implemented the change now.
So what you really need is a way to pick and choose the revisions that
go into your stable copy, not the individual files.
HTH,
arturo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to archive@mail-archive.com
