Re: wishlist: git info

From: Jakub Narebski <jnareb@gmail.com>
Date: Nov 13, 2007, 14:20 UTC
Message-ID: <fhcbrr$ef$3@ger.gmane.org>
In-Reply-To: <fhbrll$ceq$1@ger.gmane.org>

Jakub Narebski wrote:

> Thomas Neumann wrote:

Show 8 quoted lines

> You can always write[*1*] git-info.sh or git-info.perl, and install
> it as git-info in your git installation. And send patches here, to git
> mailing list, for comments.
> 
> Footnotes:
> ----------
> [*1*] Even if one of the most common complaints is "too many user-visible
>       commands".

On the other hand one of the proposed and long requested features is git-explain, which is meant to show status of git command progress. If you could incorporate proposed features in git-info (perhaps only with some option: --state, --explain, -v / --verbose,...) there would be no complaints about yet another git command.

What git-info / git-explain should show:
 * interrupted fetch / fetch in progress
 * interrupted pull  / pull  in progress
 * interrupted merge / merge in progress
 * interrupted commit, commit --amend, or tag editing
 * rebase in progress (including interactive rebase and rebasing
   using merge engine)
 * git-am (apply mbox) in progress

Perhaps we should also include git-count-objects in git-info, like git-verify-tag functionality was included in 'git tag --verify'...

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git