This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Git and GCC
On Dec 5, 2007 1:40 PM, Daniel Berlin <dberlin@dberlin.org> wrote:
>
> > Out of curiosity, how much of that is the .git/svn directory? This is
> > where git-svn-specific data is stored. It is *very* inefficient, at
> > least for the 1.5.2.5 version I'm using.
> >
>
> I was only counting the space in .the packs dir.
In my personal client, which includes the entire history of GCC, the
packs dir is only 652MB.
Obviouisly, you're not a big fan of Git, and you're entitled to your
opinion. I, however, find it very useful. Given a choice between Git
and Mercurial, I choose git, but only because I have prior experience
working with the Linux kernel. From what I've heard, both do the job
reasonably well.
Thanks to git-svn, using Git to develop GCC is practical with or
without explicit support from the GCC maintainers. As I see it, the
main barrier is the inordinate amount of time it takes to bring up a
repository from scratch. As has already been noted, Harvey has
provided a read-only copy, but it (a) only allows access to a subset
of GCC's branches and (b) doesn't provide a mechanism for developers
to push changes directly via git-svn.
This sounds like a homework project. I'll do some investigation and
see if I can come up with a good bootstrap process.
Ollie