From: Junio C Hamano <gitster@pobox.com>
To: "Steven Walter" <stevenrwalter@gmail.com>
Cc: "Santi Béjar" <sbejar@gmail.com>,
"Stephen R. van den Berg" <srb@cuci.nl>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: [RFC/PATCH] git-what: explain what to do next
Date: Tue, 27 May 2008 13:24:37 -0700 [thread overview]
Message-ID: <7v3ao31omy.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <e06498070805271108t66a45abfy9abb5ed065e59e35@mail.gmail.com> (Steven Walter's message of "Tue, 27 May 2008 14:08:35 -0400")
"Steven Walter" <stevenrwalter@gmail.com> writes:
> Surely it has happened to everyone that you start a rebase, walk away
> and then continue hacking and committing with the rebase still in
> progress. It isn't too bad for an experienced user to recover from
> this state, but prevention is much better than cure. A simple "git
> what" command that could remind you of what you were doing would be a
> welcome addition, in my mind.
I haven't looked at the patch in question, but I'd agree with the above,
and that is why I use the $PS1 support in bash completion (especially the
resent one can tell between "am" and "rebase", which made it even nicer).
next prev parent reply other threads:[~2008-05-27 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 8:34 [RFC/PATCH] git-what: explain what to do next Santi Béjar
2008-05-27 10:53 ` Johannes Schindelin
2008-05-27 12:58 ` Santi Béjar
2008-05-27 13:12 ` Johannes Schindelin
2008-05-27 13:37 ` Santi Béjar
2008-05-27 13:52 ` Stephen R. van den Berg
2008-05-27 14:21 ` Santi Béjar
2008-05-27 18:08 ` Steven Walter
2008-05-27 20:24 ` Junio C Hamano [this message]
2008-05-27 20:51 ` Junio C Hamano
2008-05-28 9:12 ` Santi Béjar
2008-05-29 4:39 ` Christian Couder
2008-05-29 5:09 ` Junio C Hamano
2008-05-29 14:56 ` Jon Loeliger
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=7v3ao31omy.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=sbejar@gmail.com \
--cc=srb@cuci.nl \
--cc=stevenrwalter@gmail.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).