[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3baede615d4733dec6f8899d24660b8c@smtp.hushmail.com>
Date: Thu, 02 Aug 2012 22:33:56 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: git repo
On 2012-08-02 22:03, magnum wrote:
> Please don't commit anything to the GitHub repos until firther notice.
> I'm merging stuff.
Jim, all
The above is no longer true, please pull and feel free to push.
I have now merged fixes -> magnum-jumbo -> bleeding and I think I fixed
most issues or merge needs (format struct upgrades) that arised. All
pass -t=0 for me. Please review (or test). Specifically, whatever
changes was applied to cryptsha256_fmt.c in -fixes was NOT merged
downstream yet, because there's just too much difference between them
for me to grasp quickly. Other than that, I *think* I merged the fixes
and kept the differences that should be kept.
Everything should be "in sync" now. Well, except the contest tree but
you don't see that anyway. I will merge the new contest tarball into my
git tree and see what comes out.
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.
