From: Stefan Naewe <stefan.naewe@atlas-elektronik.com>
To: Jeenu V <jeenuv@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Hint for rebase in progress
Date: Fri, 18 Feb 2011 10:07:41 +0100 [thread overview]
Message-ID: <4D5E36DD.7060307@atlas-elektronik.com> (raw)
In-Reply-To: <AANLkTikY-e7pD1nnbnz_m41wn0AbyF7Fj4z8K6WuznOL@mail.gmail.com>
On 2/18/2011 9:12 AM, Jeenu V wrote:
> I was once in the middle of an interactive rebase, editing a commit
> and happened to do a git status. I could see that Git warns in red
> color "Not currently on any branch". Similarly, git branch said "* (no
> branch)". Having gone this far, wouldn't it be helpful for Git to also
> remind "Rebase in progress" or something like that, some where in
> these hints? Since git status is meant to display the current status
> of the tree, I think it's only apt for it to report so.
>
> Because, once in a active rebase session, I think there's no command
> which tells user that an interactive session is in progress (or is
> there?); gitk doesn't help either. If the user happens to take a break
> or something, it might be bit perplexing to figure out where he was,
> why it was (seeing the working directory headless).
>
Look in $OFFICIAL-GIT-REPO/contrib/completion/git-completion.bash.
Set your 'PS1' as explained there and you will see at your command
prompt if you're currently rebasing.
HTH,
Stefan
--
----------------------------------------------------------------
/dev/random says: URA Redneck if you own a homemade fur coat.
prev parent reply other threads:[~2011-02-18 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 8:12 Hint for rebase in progress Jeenu V
2011-02-18 9:07 ` Stefan Naewe [this message]
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=4D5E36DD.7060307@atlas-elektronik.com \
--to=stefan.naewe@atlas-elektronik.com \
--cc=git@vger.kernel.org \
--cc=jeenuv@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).