git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Doc: note minimum scissors line length for mailinfo

From
Evan Gates <evan.gates@gmail.com>
Date
Sep 28, 2020, 19:20 UTC
Message-ID
<C5Z8UYJS02RM.2UD0R6DCK0KX5@emg-xps>
In-Reply-To
<20200928190029.GB2285677@google.com>
On Mon Sep 28, 2020 at 12:00 PM PDT, Jonathan Nieder wrote:
Show 16 quoted lines
> 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?

Previous: Jonathan NiederNext: Kevin Daudt
Message 5 of 10 in “Doc: note minimum scissors line length for mailinfo”
  1. Doc: note minimum scissors line length for mailinfoEvan Gates, Sep 25, 2020
  2. jrnieder@gmail.comSep 28, 2020
  3. Junio C HamanoSep 28, 2020
  4. Jonathan NiederSep 28, 2020
  5. Evan GatesSep 28, 2020
  6. Kevin DaudtSep 28, 2020
  7. Doc: specify exact scissors lineEvan Gates, Sep 28, 2020
  8. Doc: show example scissors lineEvan Gates, Sep 28, 2020
  9. Junio C HamanoSep 28, 2020
  10. Junio C HamanoSep 28, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.