[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 21:08:39 CEST

John wrote:
> 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.
[snip]
> 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 server.

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/

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

If what you're after is an easy way to do it, then for a GUI client
(e.g. TortoiseSVN) you'd only need to add a "Shelve" button to the
commit dialog that under-the-hood would svn-copy, svn-switch,
svn-commit, svn-switch-back. All quite doable. "svn shelve" and "svn
unshelve" could also be simulated with a shell script quite easily.

-Nathan

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

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