From: Greg KH <greg@kroah.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Federico Vaga <federico.vaga@vaga.pv.it>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: doc: stable-api-nonsense missing link
Date: Fri, 18 Jan 2019 08:33:31 +0100 [thread overview]
Message-ID: <20190118073331.GA13493@kroah.com> (raw)
In-Reply-To: <20190118072031.GH11050@kroah.com>
On Fri, Jan 18, 2019 at 08:20:31AM +0100, Greg KH wrote:
> On Thu, Jan 17, 2019 at 03:19:53PM -0700, Jonathan Corbet wrote:
> > On Thu, 17 Jan 2019 23:14:08 +0100
> > Federico Vaga <federico.vaga@vaga.pv.it> wrote:
> >
> > > in this document
> > >
> > > Documentation/process/stable-api-nonsense.rst
> > >
> > > there is this note:
> > >
> > > <insert link to leech comment from Andrew and Linus here>
> > >
> > > Is it possible to get it fixed with the proper link? I searched for it without
> > > success. If that comment is impossible to find I will send a patch to remove
> > > that note, but first I wanted to ask you if you know where to get it.
> >
> > That sounds like a question for Greg (copied). Given that this document
> > predates the Git era, though, I suspect that whatever reference that was
> > meant to be is long since lost.
>
> It was referring to an email thread about this topic that happened at
> the time I wrote the document. Let me try to dig through my archives,
> but given that it was written well over a decade ago, I don't know if I
> will be able to find it easily...
I can't find it at the moment, so taking out the text in <...> is fine
with me.
thanks,
greg k-h
prev parent reply other threads:[~2019-01-18 7:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 22:14 doc: stable-api-nonsense missing link Federico Vaga
2019-01-17 22:19 ` Jonathan Corbet
2019-01-18 7:20 ` Greg KH
2019-01-18 7:33 ` Greg KH [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=20190118073331.GA13493@kroah.com \
--to=greg@kroah.com \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--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 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.