On Wed, Jul 20, 2011 at 2:15 AM, Evangelos Foutras <firstname.lastname@example.org> wrote:
> The past few days I've been testing a new way to maintain the svntogit
> repositories . The main change is keeping a separate branch for
> each package, in addition to the master branch which contains all
> Currently, the log pages load very slow; waiting over a minute is not
> uncommon. If we switch to the new script, we can then specify the
> package branch we want and everything should load very quickly.
> Some relevant links:
> New script and log file after running for a couple of days:
> http://pkgbuild.com/~foutrelis/svntogit/ (The first run had to update
> a week's worth of packages.
> Test repositories (click the 'refs' tab to get a list of all package branches):
> - http://pkgbuild.com/git/packages.git/
> - http://pkgbuild.com/git/community.git/
> What do you guys think? If there are no objections, I could do the
> switch (I'd need access to svntogit's $HOME on gerolde).
This is definitely a ton faster, so thanks for researching and putting
something together here.
My only thought is it is hard to capture commits across multiple
packages this way, or get an overall history but still drill down into
the package level without hitting the problem we had before. Yes, I
see master is still present there, but doing any browsing on that
history is right where we were before.
Do you have the script available you used to do this? I would like to
at least try my "rewrite into subdirctories" hack as it would still
enable commits to be on multiple packages, and using your script as a
start point would be great.