A Dilluns, 25 de maig de 2009, Ian Monroe va escriure: > 2009/5/24 Chani <chan...@gmail.com>: > >> 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 :) > > And Amarok is in extragear, so the doc folder is already separate from > the folder that will be "gitified" anyways.
You really plan moving amarok code to git and leave amarok documentation in a different server? Doesn't seem too sensible thing to do for me. Albert > > I also think that as a general rule we should be conservative in > making changes, since its hard to test anything at this point. We can > do the changes one-by-one before switching the whole of KDE. > > Ian > _______________________________________________ > Kde-scm-interest mailing list > Kde-scm-interest@kde.org > https://mail.kde.org/mailman/listinfo/kde-scm-interest _______________________________________________ Kde-scm-interest mailing list Kde-scm-interest@kde.org https://mail.kde.org/mailman/listinfo/kde-scm-interest
