[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:50:58 CEST

John wrote:
> Nathan Kidd <nathan-svn <at> spicycrypto.ca> writes:
>>Why "without branching"? That's really just another way of saving your
>>work to a different location, like TS shelving. You've probably read
> Yep I did read that one. I want to avoid branching because shelving seems to be
> a way to share and review code patches that might not be good enough to commit.

> You write code, get your collegues to review the patch, if all is well, commit.
> All this you can do with (T)SVN, I'm just thinking about ways to facilitate the
> sharing and storing of patches.

That requirements explaination is very clear. But why worry about "good
enough to commit"? The changes will be in their own tree so they won't
affect anything else. Since only diffs are being stored shouldn't be
much of a disk space issue. If files are added then they also won't
take extra space when they're copied to the trunk.

It seems storing these changes in the repository would be a perfect
place for them, no?


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:53:49 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.