On Fri, Jan 8, 2010 at 11:03 AM, James Beck <james@xxxxxxxxxx> wrote:
> I'm starting to move into alpha with this code, so I really need to have a
> system that keeps track of compatible firmware versions. The best I can
> come up with is a plain text file (or Excel spreadsheet) that lists the
> overall firmware version, and the Git hash for each individual project.
> That way, if I want to load up a particular firmware version, I can
> checkout each hash for that version. Seems foolproof, but not terribly
> easy, and somewhat annoying.
The Xorg project is currently composed of 197 separate `modules', and
I believe that (practically) each has its own Git repo.
Their solution seems to be the exact same as yours, though it involves
translating between official release numbers and commits from what I
recall, all of which uses this hand-written list:
http://cgit.freedesktop.org/xorg/util/modular/tree/module-list.txt
So, perhaps you just need to write a small script to do the checkouts
automatically for you.
Also, you could use Git tags rather than raw Git hashes. If you have
"releases", you could just make the same tag name in each Git repo, so
that checking out any particular "release" just amounts to having a
script loop through the repos and checkout the necesarry commit using
the associated tag. In fact, I suggested this to the Xorg guys not
long ago:
http://www.mail-archive.com/xorg-devel@xxxxxxxxxxx/msg03037.html
See:
http://cgit.freedesktop.org/xorg/util/modular/tree/
http://www.x.org/wiki/Development/Documentation/ReleaseHOWTO
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html