From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] reap out the dead mutt config links
Date: Fri, 27 Sep 2019 19:22:28 +0530 [thread overview]
Message-ID: <20190927135228.GA1452@ArchLinux> (raw)
In-Reply-To: <20190927013827.65860ac2@lwn.net>
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
On 01:38 Fri 27 Sep 2019, Jonathan Corbet wrote:
>On Fri, 27 Sep 2019 11:10:13 +0530
>Bhaskar Chowdhury <unixbhaskar@gmail.com> wrote:
>
>> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>> ---
>> Documentation/process/email-clients.rst | 5 -----
>> 1 file changed, 5 deletions(-)
>>
>> diff --git a/Documentation/process/email-clients.rst b/Documentation/process/email-clients.rst
>> index 5273d06c8ff6..1f920d445a8b 100644
>> --- a/Documentation/process/email-clients.rst
>> +++ b/Documentation/process/email-clients.rst
>>
>> -The Mutt docs have lots more information:
>> -
>> - http://dev.mutt.org/trac/wiki/UseCases/Gmail
>> -
>> - http://dev.mutt.org/doc/manual.html
>>
>I'm all for the removal of dead links. But...can you please resubmit the
>patch with a proper changelog saying why this change is being made?
>
>For extra credit, you could try instead to replace them with current
>links, assuming such things exist.
>
>Thanks,
>
>jon
Sure Jon. I will try to find out the url ,if that available and give
back on changelog along with explanation of why we want to remove that.
BTW , I have sent another mail stating that,before sending this
patch,hope you got it. ..but I will put that in the
next patch.
Thanks,
Bhaskar
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-09-27 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 5:40 [PATCH] reap out the dead mutt config links Bhaskar Chowdhury
2019-09-27 7:38 ` Jonathan Corbet
2019-09-27 13:52 ` Bhaskar Chowdhury [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=20190927135228.GA1452@ArchLinux \
--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 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).