From: Vegard Nossum <vegard.nossum@oracle.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>, Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, backports@vger.kernel.org,
Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"Jason A . Donenfeld" <Jason@zx2c4.com>
Subject: Re: [PATCH] docs: add backporting and conflict resolution document
Date: Wed, 8 Mar 2023 09:10:42 +0100 [thread overview]
Message-ID: <62fda799-7418-eeb9-4702-2fedc78c8e45@oracle.com> (raw)
In-Reply-To: <e70bf38e-af6a-dc63-3249-adbf168a1233@oracle.com>
On 3/7/23 12:43, Vegard Nossum wrote:
> We can probably do that, but it doesn't seem to be used much in existing
> kernel documentation, I find no existing instances of it:
>
> $ git grep '\.\._.*: http' Documentation/
> $
>
> I know that lots of people really prefer to minimize the amount of
> markup in these files (as they consume them in source form), so I'd
> really like an ack from others before doing this.
Oops, bad regex (missing a space).
$ git grep '\.\. _.*: http' Documentation/
does indeed find a bunch of places where this is used, so I guess it's
fine to do it here too.
Vegard
next prev parent reply other threads:[~2023-03-08 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 16:25 [PATCH] docs: add backporting and conflict resolution document Vegard Nossum
2023-03-05 4:03 ` Bagas Sanjaya
2023-03-07 11:43 ` Vegard Nossum
2023-03-08 8:10 ` Vegard Nossum [this message]
2023-03-11 2:42 ` Bagas Sanjaya
2023-03-14 18:43 ` Jonathan Corbet
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=62fda799-7418-eeb9-4702-2fedc78c8e45@oracle.com \
--to=vegard.nossum@oracle.com \
--cc=Jason@zx2c4.com \
--cc=backports@vger.kernel.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=stable@vger.kernel.org \
/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).