[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <026201cd554e$de0fcd40$9a2f67c0$@net>
Date: Thu, 28 Jun 2012 11:55:42 -0500
From: "jfoug" <jfoug@....net>
To: <john-dev@...ts.openwall.com>
Subject: RE: KeePass patch for jumbo-6
>From: magnum [mailto:john.magnum@...hmail.com]
> we should have defined some kind of FORMAT_STRUCT_VER when
>prepare() was introduced already.
I think Solar was talking about this a while back. It would make ability to
compile versions that have forward 'looking' items, but still build them on
a prior version, without change.
Yes, right now, it is a moot point for J6, but going fwd, we should look to
address this.
It really would be nice to have all 'non-modified' formats in bleeding to be
the format from unstable. Then when a format requires some bleeding work,
you make a branch/fork/whatever (whatever name git uses). In that way,
bleeding is simply an accumulation of branches, and these branches slowly
get merged back into the main trunk, when we deem the code to be stable
enough for jumbo. I do not know git well enough to know how this is setup.
Jim.
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.
