[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <03a7e6f6074a5987746a095a4104e958@smtp.hushmail.com>
Date: Tue, 03 Apr 2012 08:54:31 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: JtR: GPU for slow hashes
On 04/03/2012 08:36 AM, SAYANTAN DATTA wrote:
> No, your patch should *not* contain all the sources and binaries. Only
>>> send the diff / git patch.
>>> Do git add, git commit, git format-patch -r -1 to generate a git patch
>>> OR just use diff program to generate a diff.
>>>
>>
>> --
>>
> Here's the patch:Hope it is right this time.
This looks much better, but don't place the patch in a tar archive next
time. Just gzip it.
Your patch applies OK to my tree. I'll commit it. I will leave out the
OSTIMER change in x86-sse.h for now though, it's not universal. Or
perhaps we should universally set it to 0 until we get something better?
Solar?
magnum
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
