Git development
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: Daniel Trstenjak <Daniel.Trstenjak@online.de>
Cc: git@vger.kernel.org
Subject: Re: Verbose output of git commands
Date: Sun, 05 Jul 2009 16:06:33 +0200	[thread overview]
Message-ID: <vpqocrz5imu.fsf@bauges.imag.fr> (raw)
In-Reply-To: <20090705105856.GC5689@laptop> (Daniel Trstenjak's message of "Sun\, 5 Jul 2009 12\:58\:56 +0200")

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

      reply	other threads:[~2009-07-05 14:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-05 10:58 Verbose output of git commands Daniel Trstenjak
2009-07-05 14:06 ` Matthieu Moy [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=vpqocrz5imu.fsf@bauges.imag.fr \
    --to=matthieu.moy@imag.fr \
    --cc=Daniel.Trstenjak@online.de \
    --cc=git@vger.kernel.org \
    /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