svn instead of github?

[Ian Bicking <ia...@colorstudy.com>]

Hi all.  I've just started checking out libcloud, and I notice you
guys are in the middle of moving things to Apache infrastructure.
But... svn?  I am probably going to have some patches, but I'd much
rather submit them through github pull requests (plus, I'd like to use
my patched code, which is easy using github, and I'd rather not deal
with git/svn stuff at all).

-- 
Ian Bicking  |  http://blog.ianbicking.org  |  http://topplabs.org/civichacker

Re: svn instead of github?

[Tom Davis <to...@dislocatedday.com>]

Yeah, in my opinion this was the one disadvantage of moving to Apache. They
have a read-only git mirror, but that hardly approaches the simplicity we
had with the git/github solution. C'est la vie!

On Wed, Dec 9, 2009 at 4:06 PM, Ian Bicking <ia...@colorstudy.com> wrote:

> Hi all.  I've just started checking out libcloud, and I notice you
> guys are in the middle of moving things to Apache infrastructure.
> But... svn?  I am probably going to have some patches, but I'd much
> rather submit them through github pull requests (plus, I'd like to use
> my patched code, which is easy using github, and I'd rather not deal
> with git/svn stuff at all).
>
> --
> Ian Bicking  |  http://blog.ianbicking.org  |
> http://topplabs.org/civichacker
>

Re: svn instead of github?

[Tom White <to...@cloudera.com>]

For contributors, the workflow described at
http://www.apache.org/dev/git.html#workflow works pretty well. If you
create patches with "git diff --no-prefix" then committers can apply
them to the svn tree using 'patch'. This is the way we do it for
Hadoop, at least.

Cheers,
Tom

On Wed, Dec 9, 2009 at 1:11 PM, Alex Polvi <po...@cloudkick.com> wrote:
> On Wed, Dec 9, 2009 at 1:06 PM, Ian Bicking <ia...@colorstudy.com> wrote:
>> Hi all.  I've just started checking out libcloud, and I notice you
>> guys are in the middle of moving things to Apache infrastructure.
>> But... svn?  I am probably going to have some patches, but I'd much
>> rather submit them through github pull requests (plus, I'd like to use
>> my patched code, which is easy using github, and I'd rather not deal
>> with git/svn stuff at all).
>
> Continue to push your stuff to github. The git/svn details can be
> figured out by the committer. If you want to become a full blown
> committer, you might need to use git-svn... but we are still figuring
> that out.
>
> But yeah -- don't let svn keep you from contributing. Push your code
> to github, post it to the list, fedex it on parchment -- whatever it
> takes. :)
>
> Thanks for filing the bugs too.
>
> -Alex
>
>>
>> --
>> Ian Bicking  |  http://blog.ianbicking.org  |  http://topplabs.org/civichacker
>>
>
>
>
> --
> co-founder, cloudkick.com
> twitter.com/cloudkick
> 541 231 0624
>

Re: svn instead of github?

[Alex Polvi <po...@cloudkick.com>]

On Wed, Dec 9, 2009 at 1:06 PM, Ian Bicking <ia...@colorstudy.com> wrote:
> Hi all.  I've just started checking out libcloud, and I notice you
> guys are in the middle of moving things to Apache infrastructure.
> But... svn?  I am probably going to have some patches, but I'd much
> rather submit them through github pull requests (plus, I'd like to use
> my patched code, which is easy using github, and I'd rather not deal
> with git/svn stuff at all).

Continue to push your stuff to github. The git/svn details can be
figured out by the committer. If you want to become a full blown
committer, you might need to use git-svn... but we are still figuring
that out.

But yeah -- don't let svn keep you from contributing. Push your code
to github, post it to the list, fedex it on parchment -- whatever it
takes. :)

Thanks for filing the bugs too.

-Alex

>
> --
> Ian Bicking  |  http://blog.ianbicking.org  |  http://topplabs.org/civichacker
>



-- 
co-founder, cloudkick.com
twitter.com/cloudkick
541 231 0624