[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: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-08-03 02:25:20 CEST

Ben Collins-Sussman <sussman@collab.net> wrote on 08/02/2005 07:17:19 PM:

> On Aug 2, 2005, at 5:13 PM, John wrote:
> >
> > So bottom line, do you think the 'shelveset' idea is marketing-
> > b***? Nothing
> > that can't be achived just as well with branching & merging?
> It's not marketing-bull, it sounds like a very nice feature. All
> we're doing is pointing out that the same feature can be accomplished
> by "committing to a temporary branch" and "merging from a temporary
> branch" for *any* version control system. It sounds like MS has
> simply optimized this technique into a single command.

I have not read every message in this thread, but I have read a lot of
them. Has anyone pointed out that most of this functionality already
exists? The command svn copy wc url creates the shelf with just one
command. Both TortoiseSVN and Subclipse expose this in a simple UI. I
think I saw someone imply you would have to create the branch, switch to
the branch and then commit and switch back. That isn't true. You can do
it with just the one command/option.

You do typically have to either follow this with svn revert, if you want
to go back to what you were working on, or svn switch if you want to keep
working on this new branch. But it is just two commands.


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 3 02:28:23 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.