Ramkumar Ramachandra <artag...@gmail.com> writes: > Ramkumar Ramachandra writes: >> svn:sync-from-url - it's clear why svnsync needs this. After the >> `init`, subsequent calls to `sync` needs this information, but isn't >> given it explicitly. > > We can keep this. > >> svn:sync-currently-copying and svn:sync-last-merged-rev - `sync` needs >> to know how many revisions to copy. > > I looked more closely and found out that these headers have to be > updated everytime a revision is written (hooked into revstart and > revfinish functions). Since we write immediately to the stream, we > cannot use this technique- to enable resume support, we must actually > look at the tail of the dumpfile supplied and see which revision was > dumped last. Hence, I'm dropping these two headers. > >> svn:sync-from-uuid - I'm not sure why svnsync NEEDS this, but I >> suppose it's just for completeness/ elegance. > > We can keep this. > >> svn: date - I'm guessing that this is the date the repository was >> created, as opposed to the date of the original checkin. This should >> be possible to get via the RA API I think, althought I haven't figured >> out how. > > It turns out that this is a REAL revision property that I can get by > passing a 0 revision argument to svn_ra_rev_proplist.
They are all the same (REAL?), they are all just unversioned revision properties. Like Stefan I don't understand why svnrdump is inventing revsion properties. It should simply dump those that exist, it should not add anything that does not exist. -- Philip
