git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jan Engelhardt <jengelh@computergmbh.de>
Subject: Re: [PATCH] format-patch: set default stat_width to 72
Date: Fri, 4 Apr 2008 06:50:56 -0400	[thread overview]
Message-ID: <20080404105056.GB29672@sigill.intra.peff.net> (raw)
In-Reply-To: <7vr6dmywqg.fsf@gitster.siamese.dyndns.org>

On Thu, Apr 03, 2008 at 11:12:23PM -0700, Junio C Hamano wrote:

> >> format-patch already defaults to "--stat --summary -p" if you give it
> >> no format options. The default stat is 80, I believe; for format-patch
> >> it should probably be bumped to 72 anyway.
> [...]
> But it loses information, and I am not sure if it is worth it.  Why do you
> even worry about "a few layers of quoting"?  Isn't it a much worse offense
> from responder/commenter's part to quote and NOT trimming diffstat part?

I don't think a blanket rule to say "it is wrong for a responder to
quote the diffstat part" makes sense. I have several times seen people
specifically responding to the diffstat.

At any rate, I don't think the current setting is a big problem; my
thought was that we are generating an email, and that certain line
length conventions tend to apply there (though it could just as easily
be 76, or 78, or whatever convention). Losing a few characters off the
end of the diffstat doesn't really seem like information loss to me
(the +++-- part is gets chomped, and it is already being chomped for the
80-character limit; we just normalize it to a slightly smaller number of
characters).

But I don't really care that much, so please drop the patch if you are
concerned about that.

-Peff

      reply	other threads:[~2008-04-04 10:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 10:22 [PATCH] format-patch: set default stat_width to 72 Jeff King
2008-04-04  6:12 ` Junio C Hamano
2008-04-04 10:50   ` Jeff King [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080404105056.GB29672@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jengelh@computergmbh.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).