git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Arver <linusa@google.com>
To: Felipe Contreras <felipe.contreras@gmail.com>,
	Linus Arver via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "Emily Shaffer [ ]" <emilyshaffer@google.com>
Subject: Re: [PATCH] MyFirstContribution: render literal *
Date: Tue, 04 Apr 2023 22:39:17 -0700	[thread overview]
Message-ID: <owlyzg7mubui.fsf@fine.c.googlers.com> (raw)
In-Reply-To: <CAMP44s15E0xJwXv8qGp8FqQvB_KaxS2TXenNZNH_VzvXpXv4Hw@mail.gmail.com>

Hello Felipe!

Felipe Contreras <felipe.contreras@gmail.com> writes:
> Small nit: with this change we would lose the quotes, which are
> helpful, I would rather do "`foo`".

I see that the doc currently does not quote backticked areas, so this
would be introducing a new style. I think such a change should belong in
a separate patch.

That being said, personally I think having the quotes around the
backticks makes things harder to read, especially for users directly
reading from the raw *.txt file.


> And for what it's worth I would revamp the whole section, something like  
> this:

> --- a/Documentation/MyFirstContribution.txt
> +++ b/Documentation/MyFirstContribution.txt
> @@ -1136,18 +1136,18 @@ information on how to handle comments from  
> reviewers.
>   We'll reuse our `psuh` topic branch for v2. Before we make any changes,  
> we'll
>   mark the tip of our v1 branch for easy reference:

> -----
> +....
>   $ git checkout psuh
>   $ git branch psuh-v1
> -----
> +....


While I see the four dots (....) being used to denote regions in other
files like SubmittingPatches, they are not used at all in
MyFirstContribution.txt. So I am not sure why we would want to change
this.

  reply	other threads:[~2023-04-05  5:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05  2:28 [PATCH] MyFirstContribution: render literal * Linus Arver via GitGitGadget
2023-04-05  4:30 ` Felipe Contreras
2023-04-05  5:39   ` Linus Arver [this message]
2023-04-05 13:22     ` Felipe Contreras
2023-04-05 15:58       ` Linus Arver
2023-04-06  8:52         ` Felipe Contreras
2023-04-06 21:14 ` Taylor Blau

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=owlyzg7mubui.fsf@fine.c.googlers.com \
    --to=linusa@google.com \
    --cc=emilyshaffer@google.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@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.
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 NNTP newsgroup(s).