All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Pascal Terjan <pterjan@google.com>
Cc: Federico Vaga <federico.vaga@vaga.pv.it>,
	Harry Wei <harryxiyou@gmail.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Delete obsolete magic constants from documentation
Date: Fri, 22 Nov 2019 10:08:44 -0700	[thread overview]
Message-ID: <20191122100844.2e9b22c6@lwn.net> (raw)
In-Reply-To: <20191121191536.186051-1-pterjan@google.com>

On Thu, 21 Nov 2019 19:15:36 +0000
Pascal Terjan <pterjan@google.com> wrote:

> Those no longer appear in the code.
> I have some more patches to cleanup some of them from the code but this
> is an easy first step.
> 
> Signed-off-by: Pascal Terjan <pterjan@google.com>
> ---
>  Documentation/process/magic-number.rst        | 44 -------------------
>  .../it_IT/process/magic-number.rst            | 44 -------------------
>  .../zh_CN/process/magic-number.rst            | 44 -------------------
>  3 files changed, 132 deletions(-)

So I absolutely love this patch; we really need to clean this kind of
cruft out of the docs.

Unfortunately, it doesn't apply to docs-next; did you prepare it against
linux-next, perhaps?  Is there any chance I could get a version against
docs-next?

If you're up for further work on this file, it would be nice to get rid of
the 2.x "changelog" text at the beginning; I don't think that has any real
value now.

Thanks,

jon

  parent reply	other threads:[~2019-11-22 17:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 19:15 [PATCH] Delete obsolete magic constants from documentation Pascal Terjan
2019-11-22 11:59 ` Federico Vaga
2019-11-22 17:08 ` Jonathan Corbet [this message]
2019-11-23 16:48   ` Pascal Terjan

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=20191122100844.2e9b22c6@lwn.net \
    --to=corbet@lwn.net \
    --cc=federico.vaga@vaga.pv.it \
    --cc=harryxiyou@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pterjan@google.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 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.