From: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: しらいしななこ <nanako3@bluebottle.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH] stash: end commit log with a newline
Date: Thu, 5 Jul 2007 13:58:25 +0200 [thread overview]
Message-ID: <20070705115825.GA13654@informatik.uni-freiburg.de> (raw)
In-Reply-To: <7vbqere732.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> しらいしななこ <nanako3@bluebottle.com> writes:
>
> > I am sorry to join the discussion late, but I think it is much better to let
> > the user give a short reminder message from the command line. For example,
> >
> > $ git stash add customized message to stash
> >
> > When I say "git stash list", I want to see which branch I was on when I was
> > in the middle of doing something, and what that something was. It is not
> > interesting which commit on that branch I started that change from. After
> > creating a stash without a message, and then another stash with a message, I
> > want to see:
> >
> > $ git stash list
> > stash@{0}: On master: add customized message to stash
> > stash@{1}: WIP on master: 36e5e70... Start deprecating "git-command" in favor of "git command"
>
> Hmph. I only recently got interested in "stash", so have not
> enough real-life experience to base my judgement on, but I think
> I'd agree with your reasoning.
>
> Perhaps something like this?
I didn't test it yet, but it sounds good. I will apply your patch and
work a while with it. But I think if someone adds documentation, I will
give my Ack. :-)
BTW: I prefer help over usage, but if it nanako prefers usage, why not
both?
Best regards
Uwe
--
Uwe Kleine-König
http://www.google.com/search?q=1+stone%3D
next prev parent reply other threads:[~2007-07-05 11:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200707042324.l64NOp8I019289@mi0.bluebottle.com>
2007-07-05 5:46 ` [PATCH] stash: end commit log with a newline Junio C Hamano
2007-07-05 11:58 ` Uwe Kleine-König [this message]
2007-07-05 16:47 ` Junio C Hamano
2007-07-05 23:54 ` しらいしななこ
2007-07-03 8:59 Uwe Kleine-König
2007-07-03 11:29 ` Johannes Schindelin
2007-07-03 14:01 ` Uwe Kleine-König
2007-07-03 14:32 ` Jeff King
2007-07-04 5:10 ` しらいしななこ
2007-07-04 5:10 ` Junio C Hamano
2007-07-04 7:44 ` Uwe Kleine-König
2007-07-04 23:18 ` しらいしななこ
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=20070705115825.GA13654@informatik.uni-freiburg.de \
--to=ukleinek@informatik.uni-freiburg.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nanako3@bluebottle.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).