git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: jrnieder@gmail.com
Cc: Evan Gates <evan.gates@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Doc: note minimum scissors line length for mailinfo
Date: Mon, 28 Sep 2020 11:55:29 -0700	[thread overview]
Message-ID: <xmqq8sctn332.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200928183559.GA2285677@google.com> (jrnieder@gmail.com's message of "Mon, 28 Sep 2020 11:35:59 -0700")

jrnieder@gmail.com writes:

>> +	(dash "-") marks and is at least 8 bytes long ("-- >8 --") is
>
> nit: I think "characters" instead of "bytes" would focus a bit more on
> the intent.  It's true that characters and bytes coincide in this
> example, but using characters might be a bit more in the terms that
> the user is already thinking in.
>
> By the way, is this the right criterion?  Perhaps an alternative
> method would be to make "--8<--" count as a scissors like after all.
> What do you think?

Mildly negative.

It certainly was fun to declare that users can use anything that
look like perforation drawn on paper, and to pile more and more
heuristics to detect such a line.  But I think, instead of
describing all these details in the manual, telling the users to
always write "-- >8 --" and nothing else would be a better approach.

It would save them time.

Let's not waste people's time by encouraging them to be "creative"
in areas that do not make the world a better place.  How flexible
they can be when drawing the line to mark the part that recipent
can discard does not matter in the end result of their work.

Thanks.

  reply	other threads:[~2020-09-28 18:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25 19:16 [PATCH] Doc: note minimum scissors line length for mailinfo Evan Gates
2020-09-28 18:35 ` jrnieder
2020-09-28 18:55   ` Junio C Hamano [this message]
2020-09-28 19:00     ` Jonathan Nieder
2020-09-28 19:20       ` Evan Gates
2020-09-28 19:33         ` Kevin Daudt
2020-09-28 20:20 ` [PATCH v2] Doc: specify exact scissors line Evan Gates
2020-09-28 22:31   ` Junio C Hamano
2020-09-28 22:51   ` [PATCH v3] Doc: show example " Evan Gates
2020-09-28 23:41     ` Junio C Hamano

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=xmqq8sctn332.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=evan.gates@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.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.
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).