Quantcast

Verbose output of git commands

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Verbose output of git commands

Daniel Trstenjak-2

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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Verbose output of git commands

Matthieu Moy
Daniel Trstenjak <[hidden email]> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Verbose output of git commands

chakzefir
This post has NOT been accepted by the mailing list yet.
In reply to this post by Daniel Trstenjak-2
Try to execute commands with -q or --quiet flag, this provides no input at all.
Loading...