Any opinions on remerging ChangeLog? I don't
insist on it, as it became huge enough to
cause a delay on each open/save sessions.
I had no problem with large ChangeLog (using Far Manager to edit),
and it was a nicer solution, than multiple files.
Okay, I also liked it better. I'll wait a little and
restore it. It's easy to switch now, all our mpkg
processes work with both methods, so.
I'll report the results with --deltas option.
Results with deltas:
- 171MB raw dump
- 48MB .bz2
I didn't measure but it didn't seem any slower, and the bzip2
session was just a few seconds, instead of a few hours.
I hope it's compatible with sf.net repository import process.
Any information on that from anyone? The doc pages mention only
full dumps.
I think it depends on SVN version, but I guess this --deltas option
is supported for a long time, so, it should work. I do not know why
you want to make SVN dump. For backup purposes? There is "--
incremental" option also.
Teo offered the his wxHarbour source tree for inclusion
in our repository (/examples/wxh) and we agreed to retain
the revision history of it.
And unfortunately there is no other way to do this in
SVN. I'm not happy to make such rounds to accomplish
a simple task like that.
'svn copy' would be the obvious option, but it only works
inside one repo.
Maybe I'll setup GIT locally, gather some experiences,
and eventually we can switch Harbour. I don't like the GIT
web interface though (on sf.net), it also doesn't have
a rev number (can't have one), no Trac support, so it's
quite a culture shock yet. For sure a lot of projects
are migrating to it though.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
