From kde-scm-interest Fri Jul 17 08:02:15 2009 From: Simon Hausmann Date: Fri, 17 Jul 2009 08:02:15 +0000 To: kde-scm-interest Subject: Re: [Kde-scm-interest] Minutes from Today's KDE -> Git BoF Message-Id: <200907171002.15104.hausmann () kde ! org> X-MARC-Message: https://marc.info/?l=kde-scm-interest&m=124781777013361 On Wednesday 08 July 2009 06:43:42 pm ext Ian Monroe wrote: > This is the minutes Leo wrote while the meeting was going on, so its a > bit stream-of-consciousness. > > Notes from KDE + Git BOF: > > Current situation: amarok goes first, gets basic infrastructure set > up, scripty, etc. > > what do we need for the git transition? [...] > snapshot to read-only svn? (it's work, but maybe some people would like > it) > > --> NEEDED for documentation, in order to get it back into SVN > for the translators/scripty/? I took a look at this item and I think the easiest way to implement this is by using git-svn like this: 1) Setup: git svn clone svn-url-where-to-put-the-snapshots snapshots cd snapshots git remote add -f source git://...repo-url 2) Periodically: cd snapshots git fetch source git read-tree source/git-branch git commit -m "snapshot from $url at $date" git checkout . git svn dcommit With this mechanism (git read-tree) we could even provide snapshots from git to svn of just a single subdirectory from a git repository, such as the doc/ subdirectory. Now I'd like to put this all together into a script, and I'm wondering what the best place would be to put it. Does anyone have any suggestions? Also, does anyone know who exactly was looking for this "feature"? Simon _______________________________________________ Kde-scm-interest mailing list Kde-scm-interest@kde.org https://mail.kde.org/mailman/listinfo/kde-scm-interest