public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: worley@alum.mit.edu (Dale R. Worley)
To: Karel Zak <kzak@redhat.com>
Cc: kerolasa@iki.fi, util-linux@vger.kernel.org
Subject: Re: [PATCH] wall: wrap message header when it exceeds 79 characters
Date: Tue, 29 Jul 2014 12:00:04 -0400	[thread overview]
Message-ID: <201407291600.s6TG04TH024607@hobgoblin.ariadne.com> (raw)
In-Reply-To: <20140729074408.GO8533@x2.net.home> (kzak@redhat.com)

Hmmm...  It seems to me that there's an interface issue.  If you're
*sure* that the message will always be consumed by a human, wrapping
is the nice thing to do.  But if the message will sometimes have to be
extracted by an automaton, write the message without line breaks,
because it's a lot easier for a human to visually reassemble a long
line (wrapped by whatever the display container is) than it is for a
program to discern that two lines are part of the same message.

Dale

      parent reply	other threads:[~2014-07-29 16:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-27 19:01 [PATCH] wall: wrap message header when it exceeds 79 characters Sami Kerola
2014-07-29  7:44 ` Karel Zak
2014-07-29  8:27   ` Sami Kerola
2014-07-29 16:00   ` Dale R. Worley [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

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

  git send-email \
    --in-reply-to=201407291600.s6TG04TH024607@hobgoblin.ariadne.com \
    --to=worley@alum.mit.edu \
    --cc=kerolasa@iki.fi \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.org \
    /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