From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: 1.5.4-rc2 plans
Date: Fri, 21 Dec 2007 08:26:51 +0100 [thread overview]
Message-ID: <476B6ABB.6040009@viscovery.net> (raw)
In-Reply-To: <7vwsr8lwf7.fsf@gitster.siamese.dyndns.org>
Junio C Hamano schrieb:
> * Should "git stash" stop doing anything useful? I think the patch
> from Nana today may be a reasonable compromise, although I still
> think fundamentally different behaviour for the same command
> configurable per-user is not very nice (we have precedent in "git
> clean" already, though, but "git clean" is inherently dangerous
> command, and "git stash" is much more useful and the issue impacts
> more people).
IMO we should give in and play the safe game. For those who don't like to
type "git stash save" can always
git config --global alias.shelve "stash save"
git config --global alias.unshelve "stash apply"
and retrain the fingers.
-- Hannes
next prev parent reply other threads:[~2007-12-21 7:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 0:32 1.5.4-rc2 plans Junio C Hamano
2007-12-21 7:26 ` Johannes Sixt [this message]
2007-12-21 9:09 ` Mike Frysinger
2007-12-22 15:04 ` Johannes Schindelin
2007-12-22 17:54 ` Mike Frysinger
2007-12-21 8:57 ` Steven Grimm
2007-12-21 10:47 ` Pierre Habouzit
2007-12-21 10:50 ` [PATCH] git-tag: fix -l switch handling regression Pierre Habouzit
2007-12-21 16:32 ` Junio C Hamano
2007-12-21 21:18 ` Pierre Habouzit
2007-12-22 8:01 ` Junio C Hamano
2007-12-21 11:06 ` 1.5.4-rc2 plans Junio C Hamano
2007-12-21 11:13 ` Pierre Habouzit
2007-12-21 11:19 ` [PATCH] parse-options: Add a gitcli(5) man page Pierre Habouzit
2007-12-22 15:05 ` 1.5.4-rc2 plans Johannes Schindelin
2007-12-22 17:03 ` Pierre Habouzit
2007-12-22 17:16 ` Junio C Hamano
2007-12-22 17:38 ` Pierre Habouzit
2007-12-22 17:52 ` 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=476B6ABB.6040009@viscovery.net \
--to=j.sixt@viscovery.net \
--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).