[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:46:41 CEST

Ben Collins-Sussman <sussman <at> collab.net> writes:

> > 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.
> This exactly what I was thinking. "shelving" is just commiting your
> work to a temporary branch.

Hi Ben,

Do you think the repository is the best place for this? The text above implies
intrinsically creating a branch (if I follow), so wouldn't it have to make
assumptions about repos structure ('/branches' existing).

My worry is that patches may be utter junk (!) and you don't want to keep an
immutable copy of them, until approved (when they'd get committed).


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