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

Re: [GSoC PATCH 3/3] doc: gitprotocol-pack: normalize inline code formatting

From
Lorenzo Pegorari <lorenzo.pegorari2002@gmail.com>
Date
Mar 3, 2026, 01:26 UTC
Message-ID
<aaY4tQzdEGE0hfvB@lorenzo-VM>
In-Reply-To
<xmqqms0px2de.fsf@gitster.g>
On Mon, Mar 02, 2026 at 03:01:17PM -0800, Junio C Hamano wrote:
Show 27 quoted lines
> LorenzoPegorari <lorenzo.pegorari2002@gmail.com> writes:
> 
> > Uniform inline code usage for command and process names.
> >
> > Signed-off-by: LorenzoPegorari <lorenzo.pegorari2002@gmail.com>
> > ---
> >  Documentation/gitprotocol-pack.adoc | 10 +++++-----
> >  1 file changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/Documentation/gitprotocol-pack.adoc b/Documentation/gitprotocol-pack.adoc
> > index f4c9e024b0..63d3971037 100644
> > --- a/Documentation/gitprotocol-pack.adoc
> > +++ b/Documentation/gitprotocol-pack.adoc
> > @@ -117,7 +117,7 @@ process on the server side over the Git protocol is this:
> >  SSH Transport
> >  -------------
> >  
> > -Initiating the upload-pack or receive-pack processes over SSH is
> > +Initiating the 'upload-pack' or 'receive-pack' processes over SSH is
> 
> These are not `backquoted` for <tt>teletype text</tt> typesetting,
> like the other hunks in this patch do?
> 
> All other things in these three patches I found them reasonable,
> except for this hunk.
> 
> Thanks.
Thank you so much for catching all my mistakes Junio.

I misread the existing formatting: I mistook the apostrophes for backticks, and so I incorrectly assumed that the document used inline code for command and process names. In reality, the rest of the document uses italics for these elements.

I'm sending a v2 where I correctly uniform command and process names to use the italic style ASAP.

Previous: Junio C HamanoNext: Junio C Hamano
Message 6 of 15 in “doc: improve gitprotocol-pack”
  1. 0/3 doc: improve gitprotocol-packLorenzoPegorari, Mar 2, 2026
  2. 1/3 doc: gitprotocol-pack: fix pronoun-antecedent agreementLorenzoPegorari, Mar 2, 2026
  3. 2/3 doc: gitprotocol-pack: improve paragraphs structureLorenzoPegorari, Mar 2, 2026
  4. 3/3 doc: gitprotocol-pack: normalize inline code formattingLorenzoPegorari, Mar 2, 2026
  5. Junio C HamanoMar 2, 2026
  6. Lorenzo PegorariMar 3, 2026
  7. Junio C HamanoMar 3, 2026
  8. 0/3 doc: improve gitprotocol-packLorenzoPegorari, Mar 3, 2026
  9. 1/3 doc: gitprotocol-pack: fix pronoun-antecedent agreementLorenzoPegorari, Mar 3, 2026
  10. 2/3 doc: gitprotocol-pack: improve paragraphs structureLorenzoPegorari, Mar 3, 2026
  11. 3/3 doc: gitprotocol-pack: normalize italic formattingLorenzoPegorari, Mar 3, 2026
  12. 0/3 doc: improve gitprotocol-packLorenzoPegorari, Mar 3, 2026
  13. 1/3 doc: gitprotocol-pack: fix pronoun-antecedent agreementLorenzoPegorari, Mar 3, 2026
  14. 2/3 doc: gitprotocol-pack: improve paragraphs structureLorenzoPegorari, Mar 3, 2026
  15. 3/3 doc: gitprotocol-pack: normalize italic formattingLorenzoPegorari, Mar 3, 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.