From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: John Keeping <john@keeping.me.uk>
Cc: "Mathieu Liénard--Mayor" <mathieu.lienard--mayor@ensimag.fr>,
git@vger.kernel.org, Mathieu.Lienard--Mayor@ensimag.imag.fr,
Jorge-Juan.Garcia-Garcia@ensimag.imag.fr
Subject: Re: New feature discussion: git rebase --status
Date: Tue, 11 Jun 2013 15:19:44 +0200 [thread overview]
Message-ID: <vpqbo7c4wen.fsf@anie.imag.fr> (raw)
In-Reply-To: <20130611125521.GL22905@serenity.lan> (John Keeping's message of "Tue, 11 Jun 2013 13:55:21 +0100")
John Keeping <john@keeping.me.uk> writes:
> The one piece of information that I often want is the SHA1 of the commit
> that is currently being applied. Currently I have to look through my
> scrollback for the "stopping" message or poke around in .git/.
>
> Having that in the output of "git status" would be really nice,
... and should be rather easy as it is the content of
.git/rebase-merge/stopped-sha
Perhaps "git status" could say stg like "(applying 1d3fb08, 2/5)"
> output format you've posted is a big improvement over what we have at
> the moment for this case.
My idea when I wrote the item on the wiki was to keep the a very short
summary in "git status", and to put all the information one could whish
in a separate command. I'd describe it as a complement more than an
improvement ;-).
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2013-06-11 13:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 12:35 New feature discussion: git rebase --status Mathieu Liénard--Mayor
2013-06-11 12:40 ` Thomas Rast
2013-06-11 12:55 ` John Keeping
2013-06-11 13:19 ` Matthieu Moy [this message]
2013-06-11 17:18 ` Hilco Wijbenga
2013-06-11 17:23 ` Linus Torvalds
2013-06-12 10:17 ` Mathieu Liénard--Mayor
2013-06-12 11:12 ` Célestin Matte
2013-06-12 11:23 ` Mathieu Liénard--Mayor
2013-06-12 12:28 ` Antoine Pelisse
[not found] ` <CAH_OBifOeSSWB-LPT=Zv2AGEf5+nTh7yxE-1ijD0snFp3RS8Dw@mail.gmail.com>
2013-06-12 12:50 ` Mathieu Liénard--Mayor
2013-06-12 22:19 ` Junio C Hamano
2013-06-13 5:52 ` Antoine Pelisse
2013-06-13 12:19 ` Mathieu Liénard--Mayor
2013-06-12 12:41 ` Matthieu Moy
2013-06-12 12:52 ` John Keeping
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=vpqbo7c4wen.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=Jorge-Juan.Garcia-Garcia@ensimag.imag.fr \
--cc=Mathieu.Lienard--Mayor@ensimag.imag.fr \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
--cc=mathieu.lienard--mayor@ensimag.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 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.