From: Linus Arver <linusa@google.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Linus Arver via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org,
"Emily Shaffer [ ]" <emilyshaffer@google.com>
Subject: Re: [PATCH] MyFirstContribution: render literal *
Date: Wed, 05 Apr 2023 08:58:06 -0700 [thread overview]
Message-ID: <owlywn2qtj75.fsf@fine.c.googlers.com> (raw)
In-Reply-To: <CAMP44s128zFcMrK7URUK73ZmzETDRA5SNkWwoHgukZ9Q3f+5Qg@mail.gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> writes:
> "We" probably don't want to change it, *I* do. Because in AsciiDoc
> there's a difference between a listing block and a literal block, but
> the Git documentation does a very poor job of being compatible with
> AsciiDoc anyway.
TIL. I'll be happy to apply the listing block -> literal block changes
you suggested in a separate follow-up patch (probably looking at other
docs we have as well, not just for MyFirstContribution.txt).
> It doesn't even use the modern syntax.
I am new to asciidoc; if you know any other examples of modernizations
we can do, feel free to chime in. Thanks.
next prev parent reply other threads:[~2023-04-05 15:58 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
2023-04-05 13:22 ` Felipe Contreras
2023-04-05 15:58 ` Linus Arver [this message]
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=owlywn2qtj75.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).