From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: LinuxKernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] remove dead mutt url and add active mutt url
Date: Mon, 30 Sep 2019 20:56:07 +0530 [thread overview]
Message-ID: <20190930152607.GA27688@Slackware> (raw)
In-Reply-To: <20190930081310.7e3b9c52@lwn.net>
[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]
On 08:13 Mon 30 Sep 2019, Jonathan Corbet wrote:
>On Sat, 28 Sep 2019 20:43:03 +0530
>Bhaskar Chowdhury <unixbhaskar@gmail.com> wrote:
>
>> The following changes since commit 4e4327891fe2a2a4db342985bff4d4c48703c707:
>>
>> replace dead mutt url with active one. (2019-09-28 20:11:00 +0530)
>>
>> are available in the Git repository at:
>
>Bhaskar, I'm not going to take a pull request for a change like this. If
>you would like to make this change (and it seems like a useful change to
>make), please send me a patch that is:
>
> - based on docs-next
I have no clue where do I found out "docs-next" Jon. But I have
stumbled over these places..
https://github.com/torvalds/linux/commit/81a84ad3cb5711cec79f4dd53a4ce026b092c432
and this:
https://git.kernel.org/pub/scm/linux/kernel/git/rdunlap/linux-docs.git/
Now, do you want me to make changes there and sent a patch?? I am
absolutely not sure .
Kindly shed some light.
> - properly changelogged
> - demonstrated to build properly with sphinx
>
>Thanks,
>
>jon
Thanks,
Bhaskar
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-09-30 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-28 15:13 [GIT PULL] remove dead mutt url and add active mutt url Bhaskar Chowdhury
2019-09-30 14:13 ` Jonathan Corbet
2019-09-30 14:37 ` Bhaskar Chowdhury
2019-09-30 15:26 ` Bhaskar Chowdhury [this message]
2019-09-30 15:28 ` Randy Dunlap
2019-09-30 15:43 ` Bhaskar Chowdhury
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=20190930152607.GA27688@Slackware \
--to=unixbhaskar@gmail.com \
--cc=corbet@lwn.net \
--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.