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

Re: A rational svn shelve/checkpoint CLI

From: Stefan Sperling <stsp_at_apache.org>
Date: Mon, 8 Jan 2018 16:33:58 +0100

On Mon, Jan 08, 2018 at 03:29:45PM +0000, Julian Foad wrote:
> > How about a combination of new subcommands for actions which
> > tranfer working copy state from/to the shelf (used frequently),
> > and just one subcommand with options for management of the
> > shelf itself (used less frequently), like:
> >
> > svn shelve
> > svn unshelve
> > svn shelf --list
> > svn shelf --drop
> > svn shelf --diff/--show
>
> That's a totally reasonable approach, and is similar to (not exactly the
> same as) what's currently implemented on trunk and on shelve-checkpoint
> branch.
>
> FWIW you missed out 'svn save' (create a checkpoint, don't revert from WC).

That could be 'svn shelve --keep'

> The discussion of syntax for referring to a particular shelf and version is
> perhaps the more interesting part of the whole discussion; I would welcome
> any thoughts on that part.

We could assign numbers to them, display those in 'svn shelf --list',
and let all other shelf-manipulating options expect a number.

Additionally, or instead, we could have user-provided shelf entry names
(UTF-8 strings), and allow them to be used for identification.
Received on 2018-01-08 16:34:09 CET

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