From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add --summary to git-format-patch by default
Date: Wed, 17 Jan 2007 20:04:40 -0500 [thread overview]
Message-ID: <20070118010440.GA23124@spearce.org> (raw)
In-Reply-To: <7vac0hqq33.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> This adds --summary output in addition to the --stat to the
> output from git-format-patch by default.
> Opinions?
This is the right thing to do. format-patch should default to
both --summary and --stat.
--
Shawn.
next prev parent reply other threads:[~2007-01-18 1:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 21:35 [PATCH] git-format-patch -3 Junio C Hamano
2007-01-17 21:51 ` [PATCH] Add --summary to git-format-patch by default Junio C Hamano
2007-01-17 22:41 ` [PATCH] git-format-patch: make --binary on " Junio C Hamano
2007-01-17 23:06 ` [PATCH - todo] Changes to e-mailed patch handling in v1.5.0 Junio C Hamano
2007-01-18 8:18 ` Andy Parkins
2007-01-18 15:13 ` Brian Gernhardt
2007-01-18 1:04 ` Shawn O. Pearce [this message]
2007-01-18 1:25 ` [PATCH] git-format-patch -3 Johannes Schindelin
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=20070118010440.GA23124@spearce.org \
--to=spearce@spearce.org \
--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).