Re: [PATCH] Doc: note minimum scissors line length for mailinfo
- From
Kevin Daudt <me@ikke.info>
- Date
- Sep 28, 2020, 19:33 UTC
- Message-ID
- <20200928193332.GA2986883@alpha>
- In-Reply-To
- <C5Z8UYJS02RM.2UD0R6DCK0KX5@emg-xps>
On Mon, Sep 28, 2020 at 12:20:31PM -0700, Evan Gates wrote:
Show 28 quoted lines
> On Mon Sep 28, 2020 at 12:00 PM PDT, Jonathan Nieder wrote:
> > Junio C Hamano wrote:
> >
> > > 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.
> >
> > Agreed, I think this is a much better direction.
> >
> > Another advantage is that it makes us easier to change the heuristics,
> > confident that we are training users to aim for the simple and
> > reliable case instead of the edge cases that may need to be tweaked
> > over time.
>
> Sounds good to me. How about:
>
> Remove everything in body before a scissors line ("-- >8 --"). The line
> represents scissors and perforation marks, and is used to request the
> reader to cut the message at that line. If that line appears in the
> body of the message before the patch, everything before it (including
> the scissors line itself) is ignored when this option is used.
>
> Etiquette question: Should a v2 patch be a new thread or reply to
> this one?Typically you would reply to this thread, ie, to 20200925191659.31375-1-evan.gates@gmail.com
Kevin