From: Daniel Trstenjak <Daniel.Trstenjak@online.de>
To: git@vger.kernel.org
Subject: Verbose output of git commands
Date: Sun, 5 Jul 2009 12:58:56 +0200 [thread overview]
Message-ID: <20090705105856.GC5689@laptop> (raw)
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
next reply other threads:[~2009-07-05 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-05 10:58 Daniel Trstenjak [this message]
2009-07-05 14:06 ` Verbose output of git commands Matthieu Moy
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=20090705105856.GC5689@laptop \
--to=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