From: Michael Witten <mfwitten@gmail.com>
To: James Beck <james@jmbeck.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Linking multiple Git repositories for version tracking
Date: Fri, 8 Jan 2010 23:25:33 -0600 [thread overview]
Message-ID: <b4087cc51001082125h37fc43f0t5f2a9809f558388c@mail.gmail.com> (raw)
In-Reply-To: <op.u574cwxqn3qeew@klee>
On Fri, Jan 8, 2010 at 11:03 AM, James Beck <james@jmbeck.com> 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@lists.x.org/msg03037.html
See:
http://cgit.freedesktop.org/xorg/util/modular/tree/
http://www.x.org/wiki/Development/Documentation/ReleaseHOWTO
next prev parent reply other threads:[~2010-01-09 5:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <op.u573txvdn3qeew@klee>
2010-01-08 17:03 ` Linking multiple Git repositories for version tracking James Beck
2010-01-08 18:34 ` Avery Pennarun
2010-01-09 5:25 ` Michael Witten [this message]
2010-01-10 8:12 ` Christoph Jahn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4087cc51001082125h37fc43f0t5f2a9809f558388c@mail.gmail.com \
--to=mfwitten@gmail.com \
--cc=git@vger.kernel.org \
--cc=james@jmbeck.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).