> 2) have scripty copy the doc folder from each git-module into > documentation/ and commit it to svn (chusslove's idea). > pro: translators don't have to lift a finger, and still no pain for > packagers or developers > con: ugly. wastes disk space and svn revisions.
I talked with some translators on irc and decided to go with this option for now. that means no changes to workflow at all for the translators. it does make sense for the period where only amarok will be in git, actually, since we haven't yet *proved* git's going to work out, and I'm not sure how long it'll be before amarok's out of the guinea-pig phase :) -- This message brought to you by eevil bananas and the number 3. www.chani3.com
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
