[Cryptech Core] git, again

[Joachim Strömbergson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aloha!

(Should this be in core or tech btw, Linus?)

Rob Austein wrote:
> Proposed rule of thumb (a bit difficult to apply in the case of some 
> of this stuff, but try it on for size at conceptual level): if, in 
> something like the Debian software universe, a collection of stuff
> is sufficiently interrelated that one would use a single
> debian/control file to build one or more binary packages, it should
> be a single repository; if it would be multiple independent
> debian/control files, it's multiple projects, thus multiple
> repositories.  I realize that this does not map perfectly to the
> hardware-building universe, but I suspect the general ideas is
> clear.
> 
> RFC 1925 (5) may be relevant here :)

Yes. ;-)

There are a number of ways to slice and dice the cat. But currently (at
Github) I use one repo for each core. Each core includes any SW-models,
testbenches, local build scripts and support tools as well as
documentation. This allows me to make branches that are related only to
the core.

The problem with this is during integration, and it might be better to
have a single repo which then is forked for sub systems and we use pull
requests for the merging.

I have to little experience in managing big Github projects to claim the
high ground here. I can ask around though.

One thing I do would like to have is some test area/repo where we at
least can shake out commit privileges, commit signing etc.

- -- 
Med vänlig hälsning, Yours

Joachim Strömbergson - Alltid i harmonisk svängning.
========================================================================
 Joachim Strömbergson          Secworks AB          joachim at secworks.se
========================================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlLqEM0ACgkQZoPr8HT30QFgogCeNgcvHcCPgCYWrSubelgm3AfU
5I0AoMcdRZJj0hRItAc3CsoSotvhTuxB
=MYSL
-----END PGP SIGNATURE-----