Hi Phil, I haven't had any time to check it, sorry. I'm really busy
these days and
I am trying to balance things out. I'd really appreciate if you
contact the repo.or.cz guys
on the issue on behalf of cryptodev-linux.
regards,
Nikos
On Thu, Mar 1, 2012 at 1:44 AM, Phil Sutter <p...@nwl.cc> wrote:
> Hi,
>
> On Wed, Feb 29, 2012 at 01:19:43PM +0100, Nikos Mavrogiannopoulos wrote:
>> On Tue, Feb 28, 2012 at 11:56 PM, Phil Sutter <p...@nwl.cc> wrote:
>> > Another thing I just noticed, these commit-mails are somehow broken.
>> > E.g. backslashes are missing completely, and worse they're somehow
>> > interpreted (trailing ones make lines continue and stuff). Just in case
>> > you haven't noticed yet.
>>
>> I never noticed. I'll check, and try to report it to guys at repo.or.cz. If
>> you have already examples in mind from the archive let me know.
>
> No problem, take e.g. the mail containing my openssl_wrapper (Message-ID
> 20120228213130.af02a1472...@rover.ms.mff.cuni.cz). The printk-changes
> right at the beginning are already interesting:
> | - printf("running %sn", __func__);
> | + if (debug) printf("running %sn", __func__);
> here the mailer changed the '\n' at the end of the format string to 'n'.
> This happens every time, your test program silencing commit is a fine
> demonstration. :)
>
> Further down that mail, at the start of the next commit there is
> something like this:
> | hostprogs := cipher cipher-aead hmac speed async_cipher async_hmac
> async_speed sha_speed hashcrypt_speed fullspeed cipher-gcm -
> cipher-aead-srtp
> | + cipher-aead-srtp ${comp_progs}
> the backslashes at EOL are missing, and even the patch syntax got messed up.
>
> Hope that helps, Phil
>
> _______________________________________________
> Cryptodev-linux-devel mailing list
> Cryptodev-linux-devel@gna.org
> https://mail.gna.org/listinfo/cryptodev-linux-devel
_______________________________________________
Cryptodev-linux-devel mailing list
Cryptodev-linux-devel@gna.org
https://mail.gna.org/listinfo/cryptodev-linux-devel
