From: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>, nanako3@bluebottle.com
Subject: Re: [PATCH] stash: end commit log with a newline
Date: Wed, 4 Jul 2007 09:44:44 +0200 [thread overview]
Message-ID: <20070704074444.GA5687@informatik.uni-freiburg.de> (raw)
In-Reply-To: <7vodiskb3d.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> I noticed another thing. The entries shown in "git stash list"
> look like this:
>
> stash@{0}: js/stash: e1d32c1... Teach git-stash to "apply --index"
> stash@{1}: master: 5be6007... Rewrite "git-frotz" to "git frotz"
> stash@{2}: master: 36e5e70... Start deprecating "git-command" in favor of "git command"
> stash@{3}: master: 3b0d999... Merge branch 'jo/init'
>
> But each of the stash is _not_ about these commits, but is about
> some change that happens to be on top of them.
>
> So risking to make it a tad longer, how about doing this on top?
>
> - git update-ref -m "$msg" $ref_stash $w_commit ||
> + git update-ref -m "WIP on $msg" $ref_stash $w_commit ||
I like that. I already wondered about that, too. But not as much as
thinking about an alternative.
So:
Acked-by: Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de>
Best regards
Uwe
--
Uwe Kleine-König
http://www.google.com/search?q=gravity+on+earth%3D
next prev parent reply other threads:[~2007-07-04 7:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 8:59 [PATCH] stash: end commit log with a newline 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 [this message]
2007-07-04 23:18 ` しらいしななこ
[not found] <200707042324.l64NOp8I019289@mi0.bluebottle.com>
2007-07-05 5:46 ` Junio C Hamano
2007-07-05 11:58 ` Uwe Kleine-König
2007-07-05 16:47 ` Junio C Hamano
2007-07-05 23:54 ` しらいしななこ
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=20070704074444.GA5687@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).