From: Sanidhya Solanki <jpage.lkml@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Joe Perches <joe@perches.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: email-clients.txt
Date: Sun, 6 Dec 2015 19:10:00 -0500 [thread overview]
Message-ID: <20151206191000.280e0279@gmail.com> (raw)
In-Reply-To: <20151206111359.088bbd83@lwn.net>
So, now that everyone has sounded off about their clients, I guess we
can know how people still use the clients that are included in the
documentation.
As a side note, JC, I think I have figured out why the patch did not
apply for you but works for me. It appears, ostensibly, that when
using CLaws 3.12 on Fedora, I can send patches that seem to work only
after inserting the file. If I add anything in the compose window after
inserting the patch, the client appears to mangle it. That would
explain the issues you experienced and I still seem to be having.
As an aside, I do send every patch to myself on multiple accounts using
Claws, then compare the SHA512 hash, and as a final measure reset git
and reapply the patch. Only then do I send it to the mailing list.
If no one else provides a patch including the information supplied by
this email chain in 5 days, then I will collect it all and send it to
you in a patch.
Best give people a few days to claim their findings as their own,
without delaying it too much.
Try the patch I just send you.
Thanks.
next prev parent reply other threads:[~2015-12-07 4:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 6:09 [PATCH] Documentation: email-clients.txt Sanidhya Solanki
2015-12-06 15:30 ` Jonathan Corbet
2015-12-06 18:11 ` Joe Perches
2015-12-06 18:13 ` Jonathan Corbet
2015-12-07 0:10 ` Sanidhya Solanki [this message]
2015-12-07 4:13 ` Joe Perches
2015-12-07 5:24 ` Randy Dunlap
2015-12-06 21:35 ` Paul Bolle
2015-12-06 21:40 ` Paul Bolle
2015-12-06 20:52 ` Randy Dunlap
2015-12-07 18:16 ` Austin S Hemmelgarn
-- strict thread matches above, loose matches on Subject: below --
2015-12-07 0:01 Sanidhya Solanki
2015-12-07 8:03 ` Clemens Ladisch
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=20151206191000.280e0279@gmail.com \
--to=jpage.lkml@gmail.com \
--cc=corbet@lwn.net \
--cc=joe@perches.com \
--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.