[gst-devel] GIT test repositories
bilboed at gmail.com
Thu Oct 9 17:06:00 CEST 2008
And for those about to say "oh, but that's YET another step I need to
do", it's not true.
Those two commands are the same which are required for checking out and
updating the common module in cvs. You don't have to type those commands
for cvs because they are in the gst-autogen.sh script.
I can add a conversion to the gst-git-migration tools so that it
converts the contents of gst-autogen.sh to automatically checkout/update
the common submodule a-la-git.
On Thu, 2008-10-09 at 16:59 +0200, Edward Hervey wrote:
> git submodule init
> git submodule update
> On Thu, 2008-10-09 at 13:52 +0100, Jan Schmidt wrote:
> > On Sun, 2008-09-07 at 15:34 +0200, Edward Hervey wrote:
> > > * Using common as a git submodule
> > > git submodules are the natural way to share a module between several
> > > others. The problem was that we want to keep the coherence between
> > > checkouts of the parent module and common, so that if you check out a
> > > revision of core from a year ago, you will end up with the revision of
> > > common which was used at that time.
> > > All converted git modules have therefore been re-parsed to contain
> > > those updates and the initial .gitmodules file that contains the link to
> > > which submodule to check out and where (currently pointing to where I
> > > stored the common repository).
> > > > git checkout <acommit>
> > > > git submodule update
> > > # you will end up with common being in the state it was when
> > > # <acommit> was done.
> > >
> > I didn't have any luck with common/ - in each of core, base and -good
> > that I've tried so far, common/ is empty after cloning. I tried 'git
> > submodule update', and it stays empty.
> > Am I missing something?
> > J.
More information about the gstreamer-devel