From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Fixes for option parsing
Date: Mon, 17 Apr 2006 07:51:49 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0604170747580.3701@g5.osdl.org> (raw)
In-Reply-To: <7vu08soou3.fsf@assigned-by-dhcp.cox.net>
On Sun, 16 Apr 2006, Junio C Hamano wrote:
>
> I am not sure if that belongs to diffstat flush. I was instead
> planning to move it to diff-flush code
Well, that's broken right now with the stat part, for some reason.
> and show it only when we actually show any diffs. IOW, I think we would
> want it even when we are doing "--pretty -p", not "--pretty
> --patch-with-stat".
I'd personally prefer to see it only in front of diffstat, and leave the
patches the way they have been before. For patches, I find the indentation
of the commit message to be visually (a) much more pleasing and (b) more
pronounced than a "---" anyway.
Perhaps configurable? git-format-patch doesn't want the indentation (and
thus "---" makes sense for both patches and diffstat), while "git log"
definitely does, because it's much more visually clear _and_ it makes the
header/comment structure totally unambiguous.
Linus
next prev parent reply other threads:[~2006-04-17 14:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-16 22:17 Fixes for option parsing Linus Torvalds
2006-04-17 0:29 ` Junio C Hamano
2006-04-17 2:42 ` Linus Torvalds
2006-04-17 3:03 ` Linus Torvalds
2006-04-17 3:36 ` Junio C Hamano
2006-04-17 14:51 ` Linus Torvalds [this message]
2006-04-17 18:59 ` Log message printout cleanups Linus Torvalds
2006-04-17 22:45 ` Junio C Hamano
2006-04-17 23:59 ` Linus Torvalds
2006-04-18 0:22 ` Junio C Hamano
2006-04-18 0:37 ` Junio C Hamano
2006-04-18 0:57 ` Linus Torvalds
2006-04-18 5:52 ` Junio C Hamano
2006-04-18 15:37 ` Linus Torvalds
2006-04-18 16:06 ` Linus Torvalds
2006-04-18 16:48 ` Junio C Hamano
2006-04-18 18:33 ` [PATCH] diff --stat: make sure to set recursive Junio C Hamano
2006-04-18 0:43 ` Log message printout cleanups Linus Torvalds
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=Pine.LNX.4.64.0604170747580.3701@g5.osdl.org \
--to=torvalds@osdl.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).