From: Matthieu Moy <matthieu.moy@imag.fr>
Date: Sun, 05 Jul 2009 14:06:33 GMT
Subject: Re: Verbose output of git commands
Message-ID: <vpqocrz5imu.fsf@bauges.imag.fr>
In-Reply-To: <20090705105856.GC5689@laptop>

Daniel Trstenjak <Daniel.Trstenjak@online.de> writes:

> E.g:
> git status
>
> file: needs merge
> # Not currently on any branch.
> # Changed but not updated:
> #   (use "git add <file>..." to update what will be committed)
> #   (use "git checkout -- <file>..." to discard changes in working directory)
> #
> #       unmerged:   file
> #
> # Untracked files:
> #   (use "git add <file>..." to include in what will be committed)
> #
> #       init
>
>
> The core information is just:
>
> unmerged : file
> untracked: init

The

# Not currently on any branch.

also contains some relevant information.

> It would be nice to be able to configure an expert mode, in which only
> the core information of the git commands is printed out.

Agreed, but even without that, I find 'ui.color = true' to solve most
of the issue: the relevant text is shown colored, and the color tells
me whether the change is staged or not. So, I can still concentrate on
the important.

Other than that, "git diff --name-status" can help, too.

-- 
Matthieu