From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Alex Shi <alex.shi@linux.alibaba.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc: add translation disclaimer
Date: Sat, 23 Mar 2019 18:37:09 +0100 [thread overview]
Message-ID: <2719899.4lLstzLvQ9@harkonnen> (raw)
In-Reply-To: <20190319073539.1f16831a@lwn.net>
On Tuesday, March 19, 2019 2:35:39 PM CET Jonathan Corbet wrote:
> On Tue, 19 Mar 2019 09:03:53 +0100
>
> Federico Vaga <federico.vaga@vaga.pv.it> wrote:
> > > Oh well, I went ahead and applied it. I do think that it might make
> > > sense
> > > to move the TOC *above* the disclaimer, though, since that's what
> > > readers
> > > are really going to be interested in.
> >
> > No, problem I can do it and send a new version
>
> Note that I said I applied the patch, so "a new version" isn't quite
> what's needed here.
Actually I've sent the V2 patch with fixes suggested by Rasmus Villemoes
before you applied this (V1) patch. And in that patch the TOC is, indeed,
above.
https://lkml.org/lkml/2019/3/15/714
When I answered you talking about a new version I forgot that it was done
already (V2 patch above) ^_^'
> If you feel so inclined, a patch to reorder that file
> would be good, though.
I will send a patch that fixes this misunderstanding
> Thanks,
>
> jon
prev parent reply other threads:[~2019-03-23 17:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 20:45 [PATCH] doc: add translation disclaimer Federico Vaga
2019-03-15 5:49 ` Alex Shi
2019-03-15 8:09 ` Federico Vaga
2019-03-15 23:00 ` Federico Vaga
2019-03-15 10:00 ` Rasmus Villemoes
2019-03-15 10:55 ` Federico Vaga
2019-03-18 17:35 ` Jonathan Corbet
2019-03-19 8:03 ` Federico Vaga
2019-03-19 13:35 ` Jonathan Corbet
2019-03-23 17:37 ` Federico Vaga [this message]
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=2719899.4lLstzLvQ9@harkonnen \
--to=federico.vaga@vaga.pv.it \
--cc=alex.shi@linux.alibaba.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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