[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 23:39:13 CEST

Nathan Kidd <nathan-svn <at> spicycrypto.ca> writes:

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

Hi Nathan,

That would be cool, it's simple and doesn't require any changes to (T)SVN!.. I'm
in two minds about this and I'd like lots of people to give input :)

One argument for shelvesets is the immutability of the repository. You really
want to keep junk out of there (is this some freudian thing about not trusting
my co-workers??).

It all comes down to quality of committed code I guess. Is it ok to commit
broken, semi-written work to a branch? (so you can switch back to trunk or
another branch, and work on something else). The classic solution (branch &
switch) does appeal to me, it's elegant and like much of SVN, apparently simple.
(no disrespect, I know it's *very* clever under the hood!).

If we went down the 'shelveset' route, I don't think the SVN core is the place
to put it - it's a great versioned file system, and why pollute that? My
preferred option would be to alter TSVN to communicate via SOAP with some other
server (db based?), that would manage the 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 23:45:17 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.