From: Holger Hellmuth <hellmuth@ira.uka.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Sidney San Martín" <s@sidneysm.com>, git@vger.kernel.org
Subject: Re: [PATCH] Support wrapping commit messages when you read them
Date: Tue, 14 Feb 2012 13:10:59 +0100 [thread overview]
Message-ID: <4F3A4F53.9030302@ira.uka.de> (raw)
In-Reply-To: <7vzkcmbcbq.fsf@alter.siamese.dyndns.org>
On 13.02.2012 23:25, Junio C Hamano wrote:
> "Computers are good at automating" is true, and that is why real editors
> give an easy way to auto-wrap long prose in a paragraph while composing.
> But "computers are good at automating" is not a convincing justification
> to let the composer leave unreasonably long lines in the commit log object
> and force the reader side to line-wrap the mess only to fix it up.
Maybe this is more convincing: Only the reader side knows the
line-length of the display or window.
next prev parent reply other threads:[~2012-02-14 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-25 5:05 [PATCH] Support wrapping commit messages when you read them Sidney San Martín
2011-12-25 9:57 ` Junio C Hamano
2012-02-13 21:26 ` Sidney San Martín
2012-02-13 22:25 ` Junio C Hamano
2012-02-14 12:10 ` Holger Hellmuth [this message]
2012-02-20 21:09 ` Sidney San Martín
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=4F3A4F53.9030302@ira.uka.de \
--to=hellmuth@ira.uka.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=s@sidneysm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.