linux-kernel - Re: [PATCH] Documentation: email-clients.txt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20151206191000.280e0279@gmail.com>
Date:	Sun, 6 Dec 2015 19:10:00 -0500
From:	Sanidhya Solanki <jpage.lkml@...il.com>
To:	Jonathan Corbet <corbet@....net>
Cc:	Joe Perches <joe@...ches.com>, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: email-clients.txt

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/