[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-scm-interest
Subject:    Re: [Kde-scm-interest] Minutes from Today's KDE -> Git BoF
From:       Simon Hausmann <hausmann () kde ! org>
Date:       2009-07-17 8:02:15
Message-ID: 200907171002.15104.hausmann () kde ! org
[Download RAW message or body]

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
[prev in list] [next in list] [prev in thread] [next in thread]