Why for have you done this?

>From now on where will be latest development code?

Roman

On 21/03/2009, Tejas Dinkar <tejasdin...@gmail.com> wrote:
> Hey all,
>
> I've cloned the entire KDE4 history of kopete (since r615086) at
> github.com using git-svn. The entire history fits in 14MB, much less
> than the 29MB of files, or the 44MB SVN Checkout. Hooray!!
>
> http://github.com/gja/kopete/
>
> Also note that since r932873, kopete builds outside of kdenetwork
>
> You can change the svn credentials using the script called
> git-kde-svn-addcredentials
> ( http://gja.in/pub/git-kde-svn-addcredentials ).
> This ties the checkout to a particular svn username, and can only be
> done once. (see below for example usage) Sorry, this does not work with
> anonsvn :(.
>
> Anyone who wants to use kopete using git-svn can just do the following
> steps:
> 1) Clone my repository (or fork, if you wish)
>    $ git clone git://github.com/gja/kopete.git
> 2) Change into the new directory
>    $ cd kopete
> 3) Download the script, and execute it to set the username and path
>    $ git-kde-svn-addcredentials <username> trunk/KDE/kdenetwork/kopete
> 4) Update the repository (this step regenerates git-svn's cache)
>    $ git svn rebase
> 5) Branch, and do your work :)
>    $ git checkout -b mybranch
>
> Please note that the script in step 3 removes the remote called origin.
> This means you cannot pull/push back to (my) git repo. Use git-svn
> rebase and dcommit to keep your repository up to date.
> --
> Tejas Dinkar
> http://gja.in
> _______________________________________________
> kopete-devel mailing list
> kopete-devel@kde.org
> https://mail.kde.org/mailman/listinfo/kopete-devel
>
_______________________________________________
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel

Reply via email to