From: Miles Bader <miles@gnu.org>
To: Thomas Rast <trast@student.ethz.ch>
Cc: Daniel Trstenjak <Daniel.Trstenjak@science-computing.de>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, spearce@spearce.org
Subject: Re: [PATCH] Showing stash state in bash prompt
Date: Fri, 15 May 2009 09:57:20 +0900 [thread overview]
Message-ID: <buo1vqrqj2n.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <200905142025.02592.trast@student.ethz.ch> (Thomas Rast's message of "Thu, 14 May 2009 20:24:21 +0200")
Thomas Rast <trast@student.ethz.ch> writes:
> But IMHO it would not be a good idea to teach people stash/pop anyway:
> 'stash drop' is irreversible, because the stash is itself implemented
> through the reflog and thus not guarded by one.
I don't understand why you say this -- sure "drop" is dangerous, but
that's exactly why you should use "pop" instead, because it makes sure
the changes are _somewhere_. I found with the old (pre-"pop") stash,
I'd often end up in a situation where I'd lose track of whether I had
done a stash apply or not, and the risk of inadvertently doing a drop
_without_ a corresponding apply was very real.
stash/pop is safer, more convenient, and I think it better matches how
people actually work.
-Miles
--
What the fuck do white people have to be blue about!? Banana Republic ran
out of Khakis? The Espresso Machine is jammed? Hootie and The Blowfish
are breaking up??! Shit, white people oughtta understand, their job is to
GIVE people the blues, not to get them! -- George Carlin
next prev parent reply other threads:[~2009-05-15 0:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 9:44 [PATCH] Showing stash state in bash prompt Daniel Trstenjak
2009-05-13 10:53 ` Sverre Rabbelier
2009-05-13 11:25 ` Daniel Trstenjak
2009-05-13 19:14 ` Junio C Hamano
2009-05-14 18:24 ` Thomas Rast
2009-05-15 0:57 ` Miles Bader [this message]
2009-05-15 2:11 ` Jeff King
2009-05-15 6:39 ` John Tapsell
2009-05-15 7:01 ` Brian Gernhardt
2009-05-15 7:12 ` Miles Bader
2009-05-28 9:40 ` [RFC PATCH] Documentation: teach stash/pop workflow instead of stash/apply Thomas Rast
2009-05-29 0:59 ` Sitaram Chamarty
2009-05-29 5:37 ` Junio C Hamano
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=buo1vqrqj2n.fsf@dhlpc061.dev.necel.com \
--to=miles@gnu.org \
--cc=Daniel.Trstenjak@science-computing.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.org \
--cc=trast@student.ethz.ch \
/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.