Re: Site management strategies with Subversion
Re: Site management strategies with Subversion
- Subject: Re: Site management strategies with Subversion
- From: email@hidden
- Date: Tue, 14 Mar 2006 10:20:40 -0800
On Mar 14, 2006, at 9:53 AM, Arturo Perez wrote:
So what you really need is a way to pick and choose the revisions
that go into your stable copy, not the individual files.
You may be right. Let me tell you how I envision this, and you can
tell me if I'm wrong (please!).
Let's say I check in some changes to frameworkA, which is part of
some ongoing work. This is revision 50. Then I check in some
changes to frameworkB, which is just a small tweak and needs to get
pushed to the live site right away. This is revision 51.
Now, if I push revision 51 to the live site, don't I get the current
state of all files, which includes the stuff I checked in at revision
50 and don't want to push yet?
You are correct that what I want in this case is the delta that
revision 51 represents, though that is not always true; I don't
always commit an entire change once, and only once. One file might
get checked in several times by itself, after the first commit that
has them all.
It may be that in order to work with Subversion I'm going to have to
stop checking in work in progress, but that is sort of a shame. I
have, on occasion, messed things up so thoroughly that I've had to
recover a few files from CVS so I could back out the disastrous change.
thanks,
janine
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden