Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Martin Storsjö <martin@ma...> - 2009-08-07 14:40:33
People have pointed out that the current git repository is very large
(over 50 MB), which makes clones unnecessarily large and slow. This is due
to one commit far back in the history where the whole upstream opencore
tree was copied in, even if all non-amr parts were removed a few commits
The remedy to this is rewriting the history, so that the commits adding
and removing the superfluous files are merged into one, just adding the
files that are kept later. I tried doing such a rewriting, and got the
repository shrunk to 1.5 MB.
The downside, of course, is that our master branch would diverge from all
old clones. To fix up a clone, one would either do "git fetch origin; git
reset --hard origin/master" (or just wipe and reclone), or if one has
local commits, "git fetch origin; git rebase -i origin/master", and remove
the two merged commits during the interactive rebase.
Also, the old tags pointing to the 0.1.0 and 0.1.1 releases would have to
be removed and remade.
Please give me your opinion on this, so we can decide what to do.