From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Andreas Ericsson <ae@op5.se>
Cc: Sebastian Harl <sh@tokkee.org>,
Junio C Hamano <gitster@pobox.com>,
Benoit Sigoure <tsuna@lrde.epita.fr>,
git@vger.kernel.org
Subject: Re: git-stash: RFC: Adopt the default behavior to other commands
Date: Tue, 18 Dec 2007 15:15:37 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0712181513060.23902@racer.site> (raw)
In-Reply-To: <4767E07A.2020100@op5.se>
Hi,
On Tue, 18 Dec 2007, Andreas Ericsson wrote:
> Johannes Schindelin wrote:
>
> > In the alternative, you could just scrap all those default actions,
> > showing synopses instead. For all commands, including "git commit",
> > "git log", "git fetch", etc.
>
> Like we do for the git wrapper, you mean? Yes, that would be one
> solution, although not a very good one for all commands.
Exactly. Not a good one.
> It's probably not a bad idea for commands where the primary use is
> something else than producing visual output though, such as tag or
> branch, but those handle creation/deletion of stuff, so the default
> action for them is to list stuff of the kind they operate on. I fail to
> see why stash should be any different.
I also fail to see why stash should be any different. And that's why I
expect it to have a default operation, which is -- you guessed it --
"stash the changes!"
If I am not sure what I am about to do, there is -- wonder of wonders --
the "-h" option! And indeed:
$ git stash -h
Usage: /home/gitte/bin/git-stash [ | save | list | show | apply |
clear | create ]
So what exactly was your point again?
Ciao,
Dscho
next prev parent reply other threads:[~2007-12-18 15:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 11:03 git-stash: RFC: Adopt the default behavior to other commands Sebastian Harl
2007-12-17 22:32 ` Benoit Sigoure
2007-12-17 23:00 ` Junio C Hamano
2007-12-17 23:32 ` Benoit Sigoure
2007-12-18 0:31 ` Junio C Hamano
2007-12-18 10:59 ` Sebastian Harl
2007-12-18 12:33 ` Johannes Schindelin
2007-12-18 14:22 ` Andreas Ericsson
2007-12-18 14:47 ` Johannes Schindelin
2007-12-18 15:00 ` Andreas Ericsson
2007-12-18 15:15 ` Johannes Schindelin [this message]
2007-12-18 15:28 ` Andreas Ericsson
2007-12-18 15:40 ` Jakub Narebski
2007-12-18 16:06 ` Andreas Ericsson
2007-12-18 16:11 ` Johannes Schindelin
2007-12-18 17:40 ` Sergei Organov
2007-12-18 18:03 ` Johannes Schindelin
2007-12-18 23:31 ` Martin Langhoff
2007-12-18 15:28 ` Wincent Colaiuta
2007-12-18 15:42 ` Jörg Sommer
2007-12-18 22:13 ` Johannes Schindelin
2007-12-18 22:22 ` Junio C Hamano
2007-12-20 21:40 ` しらいしななこ
2007-12-20 22:31 ` Junio C Hamano
2007-12-21 7:59 ` Wincent Colaiuta
2007-12-21 8:40 ` しらいしななこ
2007-12-18 23:32 ` André Goddard Rosa
2007-12-18 23:41 ` Martin Langhoff
2007-12-19 7:33 ` Wincent Colaiuta
2007-12-19 7:46 ` Martin Langhoff
2007-12-19 8:29 ` Andreas Ericsson
2007-12-19 12:01 ` Johannes Schindelin
2007-12-19 12:07 ` 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=Pine.LNX.4.64.0712181513060.23902@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sh@tokkee.org \
--cc=tsuna@lrde.epita.fr \
/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).