On Friday 25 March 2005 11:35 am, Patrick Burleson wrote:
> On Fri, 25 Mar 2005 10:30:02 -0600, Sean Laurent <sean@neuronfarm.com>
wrote:
> > Perforce takes an interesting approach to this which I found rather
> > useful: it allows you to group your changes into different changesets.
> > You always have a 'default' changeset, but you can easily create new
> > changesets.
>
> I actually usually create a change set called "Do not check in" on my
> system when using Perforce. It's quite handy for config files. I hope
> that someday SVN has explicit change sets like that.
Yeah, I was a big fan of this when I used Perforce at a previous job.
Especially when I was asked to fix a bug while I was in the middle of making
other changes. A typical scenario for me went like this:
1) Checkout maintenence branch.
2) Start making changes for a nasty bugfix.
3) Someone asks me to fix some minor problem.
4) I don't want to branch and I don't want to checkout another copy because I
know this fix is going to be only a couple of files. However, I want to
prevent myself from making a stupid mistake. I create a task-specific
changeset for the nasty bugfix.
5) I make the small fix and commit.
6) I continue working on the nasty bugfix.
7) Goto #3.
This was incredibly useful because it helped save me from my own stupidity.
Not sure how this would work with the Subversion client though. IIRC, the
Perforce client actually _knew_ about all the local working copies, which
made implementing this much easier I would guess.
-Sean
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 25 18:57:55 2005