From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jeff King" <peff@peff.net>, しらいしななこ <nanako3@bluebottle.com>,
GIT <git@vger.kernel.org>
Subject: Re: [PATCH] Document git-stash
Date: Sun, 1 Jul 2007 23:57:20 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707012355150.4438@racer.site> (raw)
In-Reply-To: <7vlkdz4wp3.fsf@assigned-by-dhcp.cox.net>
Hi,
On Sun, 1 Jul 2007, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> >> +(no subcommand)::
> >> +
> >> + Save your local modifications to a new 'stash', and run `git-reset
> >> + --hard` to revert them.
> >
> > For orthogonality's sake, should this be 'git-stash save', aliased to
> > just 'git-stash'? It would make this heading a little more intuitive,
> > and the very first paragraph (describing all of the modes) a little more
> > clear.
>
> I would further suggest that we _require_ 'git stash save' to
> create a new one and perhaps make the non-subcommand case run
> 'git stash list'. While I was trying the code out I
> accidentally created a new stash when I did not mean to, which
> pushed the stash I wanted to apply down in the list every time I
> made such a mistake.
Well, the normal thing you want to do if you say "git stash" is best
described by "Git, stash!".
However, unstash would by a nice feature. Not easy, but nice. Not easy,
because we would be actively outsmarting the reflog machinery we use for
the stash.
Ciao,
Dscho
next prev parent reply other threads:[~2007-07-01 22:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 1:29 [PATCH (2nd try)] Add git-stash script しらいしななこ
2007-06-30 2:05 ` Johannes Schindelin
2007-06-30 5:37 ` [PATCH (3rd " しらいしななこ
2007-06-30 6:12 ` Jeff King
2007-06-30 6:25 ` Junio C Hamano
2007-06-30 15:41 ` Johannes Schindelin
2007-06-30 17:19 ` Junio C Hamano
2007-06-30 23:27 ` しらいしななこ
2007-06-30 15:44 ` [PATCH] Add a manual page for git-stash Johannes Schindelin
2007-06-30 16:38 ` Frank Lichtenheld
2007-06-30 17:48 ` Johannes Schindelin
2007-06-30 18:45 ` Frank Lichtenheld
2007-06-30 17:44 ` Junio C Hamano
2007-06-30 17:56 ` Johannes Schindelin
2007-06-30 18:13 ` Junio C Hamano
2007-06-30 18:44 ` Johannes Schindelin
2007-07-01 5:26 ` [PATCH] Document git-stash しらいしななこ
2007-07-01 6:48 ` Junio C Hamano
2007-07-01 8:07 ` Jeff King
2007-07-01 8:38 ` Junio C Hamano
2007-07-01 9:06 ` しらいしななこ
[not found] ` <200707010910.l619A23c027837@mi0.bluebottle.com>
2007-07-01 9:19 ` Jeff King
2007-07-01 21:39 ` Junio C Hamano
2007-07-02 4:08 ` Jeff King
2007-07-01 21:54 ` Junio C Hamano
2007-07-01 22:57 ` Johannes Schindelin [this message]
2007-07-02 4:10 ` Jeff King
2007-07-02 10:33 ` Johannes Schindelin
2007-07-02 10:44 ` [PATCH] git-stash: Make "save" the default operation again Johannes Schindelin
2007-07-02 11:00 ` Jeff King
2007-07-02 11:15 ` Johannes Schindelin
2007-07-02 23:11 ` Junio C Hamano
2007-07-01 5:20 ` [PATCH] Add a manual page for git-stash Junio C Hamano
2007-06-30 16:06 ` [PATCH] Add tests " Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0707012355150.4438@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nanako3@bluebottle.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).