This is the mail archive of the
mailing list for the GCC project.
Re: Git and GCC
On 12/5/07, David Miller <email@example.com> wrote:
> From: "Daniel Berlin" <firstname.lastname@example.org>
> Date: Wed, 5 Dec 2007 23:32:52 -0500
> > On 12/5/07, David Miller <email@example.com> wrote:
> > > From: "Daniel Berlin" <firstname.lastname@example.org>
> > > Date: Wed, 5 Dec 2007 22:47:01 -0500
> > >
> > > > The size is clearly not just svn data, it's in the git pack itself.
> > >
> > > And other users have shown much smaller metadata from a GIT import,
> > > and yes those are including all of the repository history and branches
> > > not just the trunk.
> > I followed the instructions in the tutorials.
> > I followed the instructions given to by people who created these.
> > I came up with a 1.5 gig pack file.
> > You want to help, or you want to argue with me.
> Several people replied in this thread showing what options can lead to
> smaller pack files.
Actually, one person did, but that's okay, let's assume it was several.
I am currently trying Harvey's options.
I asked about using the pre-existing repos so i didn't have to do
this, but they were all
1. Done using read-only imports or
2. Don't contain full history
(IE the one that contains full history that is often posted here was
done as a read only import and thus doesn't have the metadata).
> They also listed what the GIT limitations are that would effect the
> kind of work you are doing, which seemed to mostly deal with the high
> space cost of branching and tags when converting to/from SVN repos.
Actually, it turns out that git-gc --aggressive does this dumb thing
to pack files sometimes regardless of whether you converted from an
SVN repo or not.