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

Re: [PATCH] doc: git-blame: convert blame to new doc format

From
Jean-Noël AVILA <jn.avila@free.fr>
Date
Jan 7, 2026, 18:44 UTC
Message-ID
<2395053.ElGaqSPkdT@piment-oiseau>
In-Reply-To
<9123496.T7Z3S40VBb@debian-mbp>
On Tuesday, 6 January 2026 22:16:02 CET Michael Lyons wrote:
Show 8 quoted lines
> > Here, let's transition to the <placeholder> format: <start>..<end> and so
> > on.
> 
> This is the continuation of my question on `<start>,<end>`: Do these also go
> to backticks or keep the underscores? My impulse is backticks, but let me
> know: `<start>..<end>` or _<start>..<end>_?
> 
> The start/end change from rev/rev makes sense.
Definitely backticks here, because this is a complex synopsis span.
Show 10 quoted lines
> 
> > > -	marked with a '*'. In the porcelain modes, we print 'ignored' and
> > > -	'unblamable' on a newline respectively.
> > > +	marked with a `*`. In the porcelain modes, we print _ignored_ and
> > > +	_unblamable_ on a newline respectively.
> > 
> > If the words are printed "verbatim", then the format is backticked:
> > `ignored` and `unblamable`.
> 
> Another one where I had backticks originally and switched them. I'm not 
super-
Show 6 quoted lines
> familiar with the porcelain parts.
> 
> > This diff is quite large. If there are no other reasons to split the patch
> > according to some semantic reason, then please split file by file.
> 
> Okay. Next try will just be blame-options for now.
You can push two commits in this series.
> 
> > That's very good for a first try. Now, I hope that you will be ok to 
review
Show 7 quoted lines
> > my patches :-)
> 
> That's very kind. I'll probably need a couple more rounds before my changes
> pass inspection, let alone be declared competent to review yours. :)
> 
> For the purposes of re-submission, should I be doing something with scissors
> on this thread, or make a new thread?

Usually, the reworked series is pushed with v2 as reply to the first mail of the first submission, using for instance:

git send-email '--in-reply-to=<20260105230220.519303-1-git@michael.lyo.nz>' v2-*.patch

JN
Previous: Michael LyonsNext: Michael Lyons
Message 4 of 9 in “doc: git-blame: convert blame to new doc format”
  1. doc: git-blame: convert blame to new doc formatMichael Lyons, Jan 5, 2026
  2. Jean-Noël AVILAJan 6, 2026
  3. Michael LyonsJan 6, 2026
  4. Jean-Noël AVILAJan 7, 2026
  5. 0/2 doc: git-blame: convert blame to new doc formatMichael Lyons, Jan 8, 2026
  6. 1/2 doc: blame-options: convert to new doc formatMichael Lyons, Jan 8, 2026
  7. 2/2 doc: git-blame: convert to new doc formatMichael Lyons, Jan 8, 2026
  8. Jean-Noël AVILAJan 8, 2026
  9. Junio C HamanoJan 11, 2026

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.