From: Jonathan Corbet <corbet@lwn•net>
To: Edward Cree <ecree.xilinx@gmail•com>,
Bagas Sanjaya <bagasdotme@gmail•com>,
ecree@xilinx•com, netdev@vger•kernel.org,
linux-net-drivers@amd•com
Cc: davem@davemloft•net, kuba@kernel•org, pabeni@redhat•com,
edumazet@google•com, linux-doc@vger•kernel.org,
jacob.e.keller@intel•com, jesse.brandeburg@intel•com,
michael.chan@broadcom•com, andy@greyhouse•net, saeed@kernel•org,
jiri@resnulli•us, snelson@pensando•io, simon.horman@corigine•com,
alexander.duyck@gmail•com, rdunlap@infradead•org,
parav@nvidia•com, roid@nvidia•com, marcin.szycik@linux•intel.com
Subject: Re: [PATCH v3 net-next] docs: net: add an explanation of VF (and other) Representors
Date: Tue, 20 Sep 2022 07:08:29 -0600 [thread overview]
Message-ID: <87h712yz02.fsf@meer.lwn.net> (raw)
In-Reply-To: <482e66b4-9dae-1376-e59a-854bfc023c59@gmail.com>
Edward Cree <ecree.xilinx@gmail•com> writes:
> On 06/09/2022 10:29, Bagas Sanjaya wrote:
>> I think by convention, footnotes should be put on bottom of the doc.
>
> Hmm, a quick and unscientific sample of Documentation/ suggests that
> many/most existing examples put the footnote shortly after the
> reference or at the end of the section, roughly as I did here. I
> looked at five rST files found by "grep \[#\]_" and all of them had
> the footnote body close to the reference.
> The placement of the footnote text in the generated output is up to
> the stylesheet / renderer, of course.
We certainly have no established convention in this area as far as I
know, and I'm not convinced we need one.
Bagas, could I ask you please to focus a bit more on doing useful work
and less on telling others how they should be working?
Thanks,
jon
next prev parent reply other threads:[~2022-09-20 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 13:55 [PATCH v3 net-next] docs: net: add an explanation of VF (and other) Representors ecree
2022-09-06 9:29 ` Bagas Sanjaya
2022-09-20 12:40 ` Edward Cree
2022-09-20 13:08 ` Jonathan Corbet [this message]
2022-09-21 14:40 ` patchwork-bot+netdevbpf
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=87h712yz02.fsf@meer.lwn.net \
--to=corbet@lwn$(echo .)net \
--cc=alexander.duyck@gmail$(echo .)com \
--cc=andy@greyhouse$(echo .)net \
--cc=bagasdotme@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=ecree.xilinx@gmail$(echo .)com \
--cc=ecree@xilinx$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=jacob.e.keller@intel$(echo .)com \
--cc=jesse.brandeburg@intel$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=kuba@kernel$(echo .)org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-net-drivers@amd$(echo .)com \
--cc=marcin.szycik@linux$(echo .)intel.com \
--cc=michael.chan@broadcom$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=parav@nvidia$(echo .)com \
--cc=rdunlap@infradead$(echo .)org \
--cc=roid@nvidia$(echo .)com \
--cc=saeed@kernel$(echo .)org \
--cc=simon.horman@corigine$(echo .)com \
--cc=snelson@pensando$(echo .)io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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