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@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Best regards
Uwe
--
Uwe Kleine-König
http://www.google.com/search?q=gravity+on+earth%3D
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
