From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/5] diff --quiet
Date: Wed, 14 Mar 2007 23:33:14 +0100 [thread overview]
Message-ID: <81b0412b0703141533q4e71e67aqaa83de45fa9e3988@mail.gmail.com> (raw)
In-Reply-To: <7vodmv7bza.fsf@assigned-by-dhcp.cox.net>
On 3/14/07, Junio C Hamano <junkio@cox.net> wrote:
> The --quiet option is silently turned off (but --exit-code is
> still in effect, so is silent output) if postprocessing filters
> such as pickaxe and diff-filter are used. For all practical
> purposes I do not think of a reason to want to use these filters
> and not viewing the diff output.
pickaxe filter can be useful in hooks to enforce policy
on use of some constructs. I can well imagine (do not
even have to imagine) a stupid company policy forbidding
commits with "\<printf\>" in them. Have no idea for
diff-filter though.
next prev parent reply other threads:[~2007-03-14 22:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 18:24 [PATCH 1/2] diff --quick Junio C Hamano
2007-03-14 21:26 ` [PATCH 1/5] Remove unused diffcore_std_no_resolve Junio C Hamano
2007-03-14 21:26 ` [PATCH 2/5] diff --quiet Junio C Hamano
2007-03-14 22:33 ` Alex Riesen [this message]
2007-03-14 22:54 ` Alex Riesen
2007-03-14 23:37 ` Junio C Hamano
2007-03-15 8:22 ` Alex Riesen
2007-03-14 23:14 ` Alex Riesen
2007-03-14 23:53 ` Junio C Hamano
2007-03-15 0:33 ` Linus Torvalds
2007-03-15 1:23 ` Junio C Hamano
2007-03-15 6:47 ` Junio C Hamano
2007-03-15 16:08 ` Linus Torvalds
2007-03-15 8:19 ` Alex Riesen
2007-03-15 10:37 ` Johannes Schindelin
2007-03-15 13:55 ` Alex Riesen
2007-03-15 17:43 ` Johannes Schindelin
2007-03-15 21:08 ` Alex Riesen
2007-03-15 21:12 ` Johannes Schindelin
2007-03-16 0:16 ` Junio C Hamano
2007-03-14 21:26 ` [PATCH 3/5] Teach --quiet to diff backends Junio C Hamano
2007-03-14 21:26 ` [PATCH 4/5] revision.c: explain what tree_difference does Junio C Hamano
2007-03-14 21:26 ` [PATCH 5/5] try-to-simplify-commit: use diff-tree --quiet machinery Junio C Hamano
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=81b0412b0703141533q4e71e67aqaa83de45fa9e3988@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).