On Wed, 19 Sep 2007, Mark Phippard wrote:
> On 9/19/07, Malcolm Rowe <malcolm-svn-dev@farside.org.uk> wrote:
...
> > Will it be recreated _empty_, or will it be repopulated with the
> > existing mergeinfo data? (I assume we need the latter behaviour
> > somewhere anyway (though perhaps we're planning to make it explicit),
> > since we'll nee some way of migrating pre-1.5-era-svnmerge.py
> > properties?)
>
> It seems like someone needs to show real problems and corruption in
> the database before we ought to go that far. I do not think it has
> anyway to populate itself from the repository contents. It just
> creates empty as a by product of making it easy for existing
> repositories to be used with 1.5.
A missing mergeinfo.db will currently be re-created empty.
> I cannot see svnmerge.py script doing anything other than converting
> the property format and letting the normal property handling routines
> populate the database.
>
> If someone needs to recreate the info, shouldn't they dump/load?
We have two separate issues dealing with migration of pre-existing
repositories, one for dealing specifically with svnmerge.py, and
another for turning copyfrom info into mergeinfo:
2875 FEATURE P3 svnadmin load should add mergeinfo for copies
2878 FEATURE P3 svnmerge.py migration script
- application/pgp-signature attachment: stored
Received on Wed Sep 19 22:51:51 2007