[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: John <jsparrow_at_ecclescollege.ac.uk>
Date: 2005-08-02 22:12:40 CEST

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
> http://mikemason.ca/2005/03/30/

Hi Nathan,

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.
In just the same way patch files fly around on the dev list. (I don't think this
is just about write-access, or lack of. It's also to do with peer-review).

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.


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:18:52 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.