All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Wincent Colaiuta <win@wincent.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: git-stash: RFC: Adopt the default behavior to other commands
Date: Wed, 19 Dec 2007 09:29:56 +0100	[thread overview]
Message-ID: <4768D684.5060300@op5.se> (raw)
In-Reply-To: <46a038f90712182346t5309448egebfd3726f4d493c5@mail.gmail.com>

Martin Langhoff wrote:
> On Dec 19, 2007 8:33 PM, Wincent Colaiuta <win@wincent.com> wrote:
>> El 19/12/2007, a las 0:41, Martin Langhoff escribió:
>>
>>> On Dec 19, 2007 4:42 AM, Jörg Sommer <joerg@alea.gnuu.de> wrote:
>>>> I vote for stash print the list, because I dropped in the pitfall.
>>> I've dropped there myself, and work with a large team where we are
>>> both fans of stash, and scarred by it. Any newcomer to git that
>>> "discovers" stash gets hit by it a dozen times, this is completely
>>> unnecesary.
>> I may be missing something here, but what's the danger here? An
> 
> Surprise. Your working directory has *just* changed under your feet.
> Maybe you have an editor with further unsaved changes that is about to
> act confused whether you undo the stash or not.
> 
>> unexpected stash is incredibly easy to revert, unless I'm missing
> 
> Once you know about it, yes it is. Once you know about the reflog, you
> can sing and dance and never be worried. But for starting users, it's
> a dangerous command.
> 
>> And nobody commented on the idea I posted earlier which
>> seems to address the concerns about newbies not knowing what "git
>> stash" with no params does:
> 
> I agree with making stash more verbose -- if the unlucky new user is
> paying close attention, they'll have instructions on to how to get out
> of trouble. But I agree more with making it "just verbose, no action"
> by default. There are two strong hints:
> 
>  - all other state-changing commands take parameters
>  - quite a few people in this list have gotten burned with it
> 
> Even after knowing pretty well how stash works, I still get mixed up
> sometimes with the 'clear/clean/list' stuff. Or have a typo in the
> command.
> 

The clear vs clean confusion has been remedied though, and you can no
longer create a named stash without using "git stash save" with a
recent enough version of git.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

  reply	other threads:[~2007-12-19  8:30 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
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 [this message]
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=4768D684.5060300@op5.se \
    --to=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=martin.langhoff@gmail.com \
    --cc=win@wincent.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 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.