[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: managing patch files

From: Nathan Kidd <nathan-svn_at_spicycrypto.ca>
Date: 2005-08-02 22:31:26 CEST

Frank Gruman wrote:
> But TortoiseSVN already has this feature. I can use the 'Create Patch'
> option to generate a diff file containing all of my modifications.
> Anyone else could take that file and use the 'Apply Patch' option to
> meld it into their working copy.

In this particular scenario, you're right, the 'Create Patch'
functionality might be used instead (though it would not easily allow
others to make changes, log their changes, etc.). In a more general
sense, though, I think easy-"shelving"-functionality (on the client
side) is still useful.

Consider Bob working on feature 'foo' all day, he's almost done but then
his boss says "drop everything you're doing and work on 'baz' for
BigCustomer". Bob's changes aren't quite done so he doesn't want to
commit yet, but he also doesn't want to risk loosing a day's work in
case his hard-drive crashes, etc. If he could click an easy
"save-to-different-location" button it would be useful.

Another use might be for code reviews. "Shelve" your changes so your
co-workers can review it before you commit the changes to the trunk.

All this would be unneeded if development was only done in
feature-branches, but that's not always practical. This would
essentially be a "feature-branch *after the fact*".


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 2 22:33:11 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.