threads / discuss / 20026

Verbose output of git commands

Subject: Verbose output of git commands

## tl;dr

2 messages between Jul 5, 2009 and Jul 5, 2009.

replies: 1people: 2as markdown or json

Daniel Trstenjak· Jul 5, 2009, 10:58 UTC · lore
Hi all,

when starting with git it's very nice to have all this helpful hints in the output of the git commands. But know, after I can handle git quite well, all this helpful hints hinder me to get the core information of the commands.

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

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.

Just some thoughts.

Greetings, Daniel

Matthieu Moy· Jul 5, 2009, 14:06 UTC · re: Daniel Trstenjak · lore

Re: Verbose output of git commands

Daniel Trstenjak <Daniel.Trstenjak@online.de> writes:
Show 21 quoted lines
> 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

← back to recent threads