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

managing patch files

From: John <jsparrow_at_ecclescollege.ac.uk>
Date: 2005-08-02 20:41:52 CEST

I've been reading about the 'shelveset' feature of the new Visual Studio Team
System, and wondering how the same could be achieved in SVN - without branching.

Quick overview: a VSTS shelveset is basically a patch file stored in the
repository (unversioned). Other people can apply it to their WC's, comment,
improve etc (permissions allowing). You can optionally revert your WC following
production of a shelveset (that's were the name comes from, shelving work).

Now SVN does all this stuff, kinda. And I'm not sure it's really SVN's role to
manage unversioned patch files (is it??). But I think it would be really great
to achieved this functionality, either using script files (and maybe an ftp
server?), extension of the client, or even some new storage mechanism on the svn

Anyone have thoughts on this? We're experimenting with storing patches in a
http-accessed database (naively versioned) using SOAP. A script file creates a
diff, pipes it to another program that sends it to the db, but it's a bit klunky.

Hmm, if we used the perl / python, can either language create graphical dialogs,
asking for comments etc? I'd like something pretty looking :)



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 2 20:49:59 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.