From: Martin Waitz <tali@admingilde.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Tilman Sauerbeck <tilman@code-monkey.de>, git@vger.kernel.org
Subject: Re: [PATCH] Removed the printf("rm 'file'") from git-rm.
Date: Tue, 27 Mar 2007 00:13:48 +0200 [thread overview]
Message-ID: <20070326221347.GI22773@admingilde.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0703252335280.4045@wbgn013.biozentrum.uni-wuerzburg.de>
[-- Attachment #1: Type: text/plain, Size: 646 bytes --]
hoi :)
On Sun, Mar 25, 2007 at 11:36:35PM +0200, Johannes Schindelin wrote:
> Why not do the common thing, and add a "--quiet" option? You can even add
> a config variable to enable it by default (for git-rm). It's not like
> git-rm is performance critical...
But when we have to add --quiet to all sorts of commands that may be
the sign that they really are too chatty.
If I want a short output I don't want to type extra options.
So adding a --verbose for those that really depend on more output
makes more sense, IMHO. (Even when I don't see any useful information
in the git-rm output, to be honest.)
--
Martin Waitz
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-03-26 22:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11747590062554-git-send-email-tilman@code-monkey.de>
2007-03-25 6:22 ` [PATCH] Removed the printf("rm 'file'") from git-rm Junio C Hamano
2007-03-25 16:38 ` Anand Kumria
2007-03-25 21:04 ` Tilman Sauerbeck
2007-03-25 21:36 ` Johannes Schindelin
2007-03-26 10:28 ` [PATCH] git-rm: add --quiet option to suppress "rm 'file'" messages Eric Lesh
2007-03-26 22:56 ` Junio C Hamano
2007-03-26 22:13 ` Martin Waitz [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=20070326221347.GI22773@admingilde.org \
--to=tali@admingilde.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=tilman@code-monkey.de \
/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;
as well as URLs for NNTP newsgroup(s).