All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: Jonathan Corbet <corbet@lwn.net>, Greg KH <gregkh@linuxfoundation.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Harry Wei <harryxiyou@gmail.com>,
	Alex Shi <alex.shi@linux.alibaba.com>,
	Federico Vaga <federico.vaga@vaga.pv.it>
Subject: Re: [PATCH v1 1/4] docs: make reporting-issues.rst official and delete reporting-bugs.rst
Date: Mon, 5 Apr 2021 09:43:39 +0200	[thread overview]
Message-ID: <ed386533-fde8-c9f0-38b4-9df40f9f90b3@leemhuis.info> (raw)
In-Reply-To: <87h7krksvu.fsf@meer.lwn.net>

On 31.03.21 21:47, Jonathan Corbet wrote:
> Greg KH <gregkh@linuxfoundation.org> writes:
> 
>> On Tue, Mar 30, 2021 at 04:13:04PM +0200, Thorsten Leemhuis wrote:
>>> Removing Documentation/admin-guide/reporting-bugs.rst will break links
>>> in some of the translations. I was unsure if simply changing them to
>>> Documentation/admin-guide/reporting-issue.rst was wise, so I didn't
>>> touch anything for now and CCed the maintainers for the Chinese and
>>> Italian translation. I couldn't find one for the Japanse translation.
>>
>> Traditionally translations catch up much later on, you shouldn't have to
>> worry about them the authors will clean them up and submit patches for
>> them when they get the chance.
> 
> Agreed.  None of the broken references actually generate warnings
> (though perhaps some should) so we can let the translators catch up on
> their own time.

Ahh, good to know.

BTW to the translators in the CC: sorry for not giving you a heads up
earlier, things were supposed to get slower, but then had to be
accelerated.

> I've applied the set and stuck in this tweak:
> 
>> FWIW, this needs a
>>
>>  s!stable/>_`!stable/>`_!
>>
>> Sorry, this slipped through. :-/ Ciao, Thorsten
> 
> while I was at it.

Great, thx everyone, that what I had hoped for when I posted it.

BTW, can't see the patches in docs-next yet, but I just assume it's just
not pushed out yet for some reason. Whatever.

Side note, FWIW: I have no further patches for the text in my queue, but
I might sent one depending on how fast the new mailing list
linux-regressions will be created (will as for that later today).

Ciao, Thorsten



  reply	other threads:[~2021-04-05  7:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30 14:13 [PATCH v1 0/4] Improve reporting-issues.rst and make it official Thorsten Leemhuis
2021-03-30 14:13 ` [PATCH v1 1/4] docs: make reporting-issues.rst official and delete reporting-bugs.rst Thorsten Leemhuis
2021-03-30 14:51   ` Greg KH
2021-03-31 19:47     ` Jonathan Corbet
2021-04-05  7:43       ` Thorsten Leemhuis [this message]
2021-03-30 14:51   ` Greg KH
2021-03-31  8:33   ` Wu X.C.
2021-04-01  4:59     ` Alex Shi
2021-03-30 14:13 ` [PATCH v1 2/4] MAINTAINERS: add entry for Documentation/admin-guide/reporting-issues.rst Thorsten Leemhuis
2021-03-30 14:13 ` [PATCH v1 3/4] docs: reporting-issues.rst: reshuffle and improve TLDR Thorsten Leemhuis
2021-03-30 15:17   ` Thorsten Leemhuis
2021-03-30 14:13 ` [PATCH v1 4/4] docs: reporting-issues: reduce quoting and assorted fixes Thorsten Leemhuis

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=ed386533-fde8-c9f0-38b4-9df40f9f90b3@leemhuis.info \
    --to=linux@leemhuis.info \
    --cc=alex.shi@linux.alibaba.com \
    --cc=corbet@lwn.net \
    --cc=federico.vaga@vaga.pv.it \
    --cc=gregkh@linuxfoundation.org \
    --cc=harryxiyou@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.