From: Dongliang Mu <mudongliangabcd@gmail.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Dongliang Mu <dzm91@hust.edu.cn>,
Nicolas Palix <nicolas.palix@imag.fr>,
Jonathan Corbet <corbet@lwn.net>,
cocci@inria.fr, linux-doc@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [cocci] [PATCH] dev-tools: fix one invalid url
Date: Tue, 14 Jun 2022 09:49:30 +0800 [thread overview]
Message-ID: <CAD-N9QUOk938-+1CtGfWNKUvWowknKScLuFXXkFAv59M=-F84g@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2206131212160.2812@hadrien>
On Mon, Jun 13, 2022 at 6:12 PM Julia Lawall <julia.lawall@inria.fr> wrote:
>
>
>
> On Mon, 13 Jun 2022, Bagas Sanjaya wrote:
>
> > On Mon, Jun 13, 2022 at 03:12:42PM +0800, Dongliang Mu wrote:
> > > From: Dongliang Mu <mudongliangabcd@gmail.com>
> > >
> > > Fix the invalid url about Semantic Patch Language
> > >
> >
> > I think what this patch doing is to point SPL reference URL from old
> > Coccinelle documentation (doc root) to actual SPL doc entry on new
> > Coccinelle page, right? If so, "fix invalid URL" may not be right patch
> > description and title.
>
> Agreed, thanks for the suggestion.
Okay. Let's modify the title to "modify SPL reference URL to actual
SPL doc entry".
BTW, I modify this URL because the previous URL cannot be accessed.
>
> julia
next prev parent reply other threads:[~2022-06-14 6:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 7:12 [cocci] [PATCH] dev-tools: fix one invalid url Dongliang Mu
2022-06-13 8:01 ` Bagas Sanjaya
2022-06-13 10:12 ` Julia Lawall
2022-06-14 1:49 ` Dongliang Mu [this message]
2022-06-24 19:37 ` Jonathan Corbet
2022-06-27 1:40 ` Dongliang Mu
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='CAD-N9QUOk938-+1CtGfWNKUvWowknKScLuFXXkFAv59M=-F84g@mail.gmail.com' \
--to=mudongliangabcd@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=cocci@inria.fr \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=julia.lawall@inria.fr \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.palix@imag.fr \
/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;
as well as URLs for NNTP newsgroup(s).