Re: [Traverso-devel] using git / QtCreator

[hollunder]

On Tue, 10 Feb 2009 09:31:11 +0000
Ingmar Vanhassel <address@hidden> wrote:

> On Mon, Feb 09, 2009 at 10:35:30PM +0100, address@hidden wrote:
> > Hi Remon,
> > from my very limited experience as git user and from second hand
> > experience through lurking I know that git doesn't come without
> > problems. Maybe the app you intend to use has a nice gui that makes
> > it easy to use but so far I've seen quite some LADs running into
> > problems. Consider trying it before switching to it entirely.
> > git is a powerful beast, don't overlook the beast part..
> > 
> > So yeah, I used it and it's fine by me but I haven't got my head
> > around it and am not very comfortable with checking out anything
> > but the master branch.
> 
> It's as simple as 
> $ git checkout otherbranch
> and to get back on master
> $ git checkout master

Maybe checkout was not the right term, I meant downloading of just the
branch that is wanted. Dunno how it is called in git terms.

> http://www.kernel.org/pub/software/scm/git/docs/everyday.html is a
> very nice introducation, and

Thanks, will have a look.

> http://www.kernel.org/pub/software/scm/git/docs/gitcvs-migration.html
> should be an interesting read if you have past CVS experience.
> 
> Anyway, while you can learn git from a relatively small subset of
> commands, which I'm sure you'll find out after reading the above
> guides, I'll try my best to answer any questions that may pop up. :)
> 
> > This might be because one can only check out the whole
> > thing anyway, if I got that right.. as said, haven't got my head
> > around it..
> 
> You can do a clone without full history, but a shallow clone, as it's
> called, isn't equally functional, so I'd never bother.
> A full traverso clone takes 7MB, and gives you complete history, so
> with todays hardware I don't really see issues with that.

I wrote a buildscript for my distribution where I needed a non-master
branch and nothing else. I don't remember what it was and don't find it
anymore, but I got it to work somehow after asking around at #git.
In such a case I think it matters a bit, as it is simply more efficient
and the other branches are not needed anyway.

I _always_ write buildscripts and had my share of trouble with other
such systems as well (example: checking out only the necessary parts of
a rather large svn repo with interdependencies, the drobilla-repo, a
horror story all by itself).

Anyway, I can live with it, or rather, I have to anyway, since a bunch
of other projects I follow closely uses it as well.

Philipp