All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anders Melchiorsen <mail@cup.kalibalik.dk>
To: git@vger.kernel.org
Subject: Usability of git stash
Date: Wed, 15 Oct 2008 21:24:52 +0200	[thread overview]
Message-ID: <87wsg9acfv.fsf@cup.kalibalik.dk> (raw)

I find the UI of git stash quite unfortunate.

First, I would prefer list to be the default action, so that typing
"git stash" in the hope of getting some help would not make me lose my
local changes.

When trying to recover from that scenario, I do "git stash apply" as
recommended by the "git stash" output. Now I still lost my index
state, all changes are unstaged.

The "git command subcommand" syntax seems different from other git
commands. For example, you do not delete a branch with "git branch
delete".

The default naming of stashes makes it hard to remember what I was
actually working on. Forcing me to give it a description (like branch
and commit do) would probably have saved me some time overall.

And finally, a "git stash clear" has quite far-reaching consequences.
Most other mistakes are easy to recover from, but not this one.


I offer these observations just for discussion. It has not been
possible for me to think of any backwards compatible improvements,
other than staying away from "git stash".


Cheers,
Anders.

             reply	other threads:[~2008-10-15 19:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 19:24 Anders Melchiorsen [this message]
2008-10-15 19:31 ` Usability of git stash Brandon Casey
2008-10-16 11:24   ` David Kastrup
2008-10-16 15:22     ` Brandon Casey
2008-10-18  9:26       ` Anders Melchiorsen
2008-10-19 18:40         ` Shawn O. Pearce
2008-10-19 21:08           ` Leo Razoumov
2008-10-19 21:49             ` Shawn O. Pearce
2008-10-19 23:12           ` Stephan Beyer
2008-10-20  9:36             ` Miles Bader
2008-10-20  0:36           ` Jeff King
2008-10-20  5:29             ` Junio C Hamano
2008-10-20  5:23         ` Miles Bader
2008-10-20  9:49         ` Andreas Ericsson
2008-10-20 16:33         ` Brandon Casey

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=87wsg9acfv.fsf@cup.kalibalik.dk \
    --to=mail@cup.kalibalik.dk \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.