[wp-hackers] GitHub + plugins.svn.wordpress.org

[Steve Taylor]

I tried that method but got this error:

------------------------------------------------------------------------
Migrating from a git-svn v1 layout...
Data from a previous version of git-svn exists, but
        .git/svn
        (required for this version (1.7.8.msysgit.0) of git-svn) does not exist.

Done migrating from a git-svn v1 layout
Error validating server certificate for 'https://plugins.svn.wordpress.org:443':

 - The certificate is not issued by a trusted authority. Use the
   fingerprint to validate the certificate manually!
Certificate information:
 - Hostname: *.svn.wordpress.org
 - Valid: from Jun 21 16:07:30 2012 GMT until Jul 15 19:04:26 2015 GMT
 - Issuer: 07969287, http://certificates.godaddy.com/repository, GoDaddy.com, In
c., Scottsdale, Arizona, US
 - Fingerprint: bf:08:a3:de:ab:e4:76:fd:d0:5d:10:d1:c8:de:19:12:5f:bf:71:25
(R)eject, accept (t)emporarily or accept (p)ermanently? t

RA layer request failed: PROPFIND request failed on '/': PROPFIND of '/': Could
not read status line: connection was closed by server. (https://plugins.svn.word
press.org) at C:\Program Files (x86)\Git/libexec/git-core\git-svn line 2139
------------------------------------------------------------------------

In any case, before I persist, can you say that this method definitely
circumvents issues that arise when you have existing GitHub and
wordpress.org SVN repos, each with separate revision histories? That
was the only sticking point with Boone Gorges' method - things fell
apart when rebasing.



On 2 July 2012 13:57, Stas Sușcov <stas at nerd.ro> wrote:
> În data de Mon, 02 Jul 2012 14:04:19 +0300, Steve Taylor
> <steve at sltaylor.co.uk> a scris:
>
>
>> Thanks for the link Stas, but apart from editing .git/config, it looks
>> like the same method as Boone Gorges' (the link I posted).
>>
>> Any thoughts on starting the process when you already have working
>> GitHub & wordpress.org SVN repos?
>
>
> This might be a dumb question, but...
> Did you even try the method with direct file editing?
>
> To explain myself, `git svn` depends a lot on the entries in your
> `svn-remote` config file.
> I'm managing BuddyPress Courseware project that lives on github, and was
> able to handle (at some point) 3 svn mirrors (and 2 git remotes), using
> `svn-remote` entries in my config file without having an issue along last ~2
> years.
>
> Also the tutorial above has the purpose of digging into the `git-svn` config
> file, this way offering a chance of ignoring `git-svn` command magic, that
> from my experience broke a lot of projects for a lot of people.
>
> Cheers.