[PATCH v2] shelve: add a shelve extension to save/restore working changes

[Matt Mackall]

On Wed, 2013-06-12 at 16:31 -0700, Bryan O'Sullivan wrote:

>  
>         d) the default shelve listings are a bit confusing:
>         @-01            [3 seconds ago]   shelved from @ (9a8c25f3):
>         shelve: add a sh...
>         @               [4 hours ago]     shelved from @ (9a8c25f3):
>         shelve: add a sh...
>         
>         Is there precedent for this format?
> 
> 
> Sort of (it's vaguely similar to "git stash list", but more
> informative), but I'm happy to discuss the format.
>  
>         The "shelved from @ (9a8c25f3):"
>         wastes valuable columns.
> 
> 
> I could drop 'shelved from ', but I think the remainder is actually of
> value.
>  
>         We seem to have bookmark/branch on the left,
>         perhaps we should just have a "base" column.
> 
> 
> The name on the left is user-settable at the time of shelving - it's
> bookmark or branch if no name is given, but you can specify a more
> helpful mnemonic name if you prefer.

Yes, I get that.

I have the bookmark/branch on the left. I don't need it on the right
unless I've actually made a choice to drop it from the left by providing
my own name. This might not seem like an issue with @ or default, but
it's going to look a little clowny with
feature-add-whizbangs-on-firefox.

I have TWO ways to add my own context to a shelve: name and message. If
I care about the bookmark/branch, I can change just the message (or pick
a name that incorporates it).

By comparison, git simply numbers its stashes, so its choice to list the
current branch in the default description isn't redundant.

-- 
Mathematics is the supreme nostalgia of our time.