I've read through the archives, but I apologize ahead of time if any of this is answered already.
1. The import tool still chokes on svn:external, correct? Any proposals on how to handle them, like converting to submodules? If not, how is progress going on removing svn:external from the existing tree? 2. The current version of the import tool, including Thiago's fix for the double UTF-8 encoding, is @ http://repo.or.cz/w/fast-export.git , correct? In particular, I'd like to lend some developer time toward the Git conversion. 3. It seems to me like whatever the next VCS is, we need to find a way to live along-side SVN for an indeterminate period of time. I wasn't around during the CVS -> SVN move, but they operated concurrently for some time, correct? Has anyone started work on a set of scripts to keep the Git tree in sync with the SVN tree; I know Thiago said the current import script is not meant for running concurrently. Still, it seems like concurrency is possible and can be made mostly automatic; totally automatic if we are willing to accept one tree "trumping" the other (it need not the the same tree the whole time). -- Boyd Stephen Smith Jr. ,= ,-_-. =. [EMAIL PROTECTED] ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.org/ \_/
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-scm-interest mailing list Kde-scm-interest@kde.org https://mail.kde.org/mailman/listinfo/kde-scm-interest
