From: Wincent Colaiuta <win@wincent.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, Wincent Colaiuta <win@wincent.com>
Subject: [PATCH] Emit helpful status for accidental "git stash" save
Date: Sat, 22 Dec 2007 15:22:49 +0100 [thread overview]
Message-ID: <1198333369-17788-1-git-send-email-win@wincent.com> (raw)
In-Reply-To: <7vmys36d7n.fsf@gitster.siamese.dyndns.org>
El 21/12/2007, a las 20:48, Junio C Hamano escribió:
> (4) A tool should support safety for clueless people when it is
> reasonable.
>
> Even though "I did not know what command foo does, so I
> tried running it and it did something unexpected" is a
> silly excuse to rob quickie "git stash" from people who
> know better, we cannot avoid the fact that there are
> clueless people. I think checking stash.iknowwhatitdoes to
> detect first-time users, and explaining what it does to
> them, may make sense. And we can take hints from the patch
> that started this thread how to do this.
>
> The decision here is that I am open to a change that
> implements the one-time safety instruction.
Here's a less invasive change that I think addresses this point (4)
that you make.
-- 8< --
Emit helpful status for accidental "git stash" save
If the user types "git stash" mistakenly thinking that this will list
their stashes he/she may be surprised to see that it actually saved
a new stash and reset their working tree and index.
In the worst case they might not know how to recover the state. So
help them by telling them exactly what was saved and also how to
restore it immediately.
Signed-off-by: Wincent Colaiuta <win@wincent.com>
---
git-stash.sh | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/git-stash.sh b/git-stash.sh
index f16fd9c..a2f3723 100755
--- a/git-stash.sh
+++ b/git-stash.sh
@@ -99,7 +99,8 @@ save_stash () {
git update-ref -m "$stash_msg" $ref_stash $w_commit ||
die "Cannot save the current status"
- printf >&2 'Saved "%s"\n' "$stash_msg"
+ printf >&2 'Saved working directory and index state "%s"\n' "$stash_msg"
+ echo >&2 '(To restore them type "git stash apply")'
}
have_stash () {
--
1.5.4.rc0.68.g15eb8-dirty
next prev parent reply other threads:[~2007-12-22 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 10:22 [PATCH] Make "git stash" configurable しらいしななこ
2007-12-21 17:23 ` Steven Grimm
2007-12-21 17:27 ` Matthieu Moy
2007-12-21 17:54 ` Junio C Hamano
2007-12-21 18:26 ` Steven Grimm
2007-12-21 19:48 ` Junio C Hamano
2007-12-22 14:22 ` Wincent Colaiuta [this message]
2007-12-22 16:22 ` [PATCH] Emit helpful status for accidental "git stash" save Junio C Hamano
2007-12-22 17:31 ` [PATCH v2] " Wincent Colaiuta
2007-12-22 17:58 ` Junio C Hamano
2007-12-22 18:44 ` Wincent Colaiuta
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=1198333369-17788-1-git-send-email-win@wincent.com \
--to=win@wincent.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).