On Sun, 27 Mar 2005 10:39:50 +0200, Saulius Grazulis <grazulis@akl.lt> wrote:
> On Friday 25 March 2005 19:55, Sean Laurent wrote:
>
> > 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.
>
> Do you change the same files that you have already started fixing for Nasty
> Bugfix?
>
> If no, you can just fix several other files, and commit just those files:
>
> svn ci first_from_only_a_couple_of_files.c second.c
>
> If yes, I do not see a viable altervnative to a genuine branch (which would
> make things more clear).
>
> Doesn't this mean that 'changesets' would just duplicate functionality of sbn
> branches and checkins?
>
The point of the change sets is to organize a certain set of files
explicitly for a particular change. The changeset has the list of
files you've associated with the change, so less of a chance of
checking in the wrong file by mistake. Instead of having to remember
which files go with each change. Very helpful if small bugfix turns
into Nasty Bug Fix 2.
Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Mar 27 22:50:02 2005