Hey Jake,

Thanks. I know what the official source repository is for OODT,
and that SVN is the canonical bits, and that the mirror at Github
is simply a mirror. I also know that merges aren't automatic and
that they can't automatically be integrated.

My question is can you configure the pull request-to-email list
notification? We should be able to do that without switching to
Git, correct? I'm not proposing to move OODT to Git. Thanks.

Cheers,
Chris



-----Original Message-----
From: Jake Farrell <[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Wednesday, January 29, 2014 9:36 PM
To: jpluser <[email protected]>
Cc: "[email protected]" <[email protected]>,
"[email protected]" <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: OODT's Git mirror at Github is borked

>Hey Chris
>The official source repository for OODT is currently in svn, and Github
>is just a mirror of that svn repository. When a pull request is issued
>against one of our mirrors on Github it can email the configured mailing
>list for that mirror that a pull request
> is available, but it can not be merged into that mirror. The Github
>notification email that is sent contains a link to the patch and the
>description or comment that was given, not the actual patch itself.
>
>
>Tika has 3 open pull requests which are 8 months old to 2 years old,
>comments can be made by anyone on them, but only Github Apache org admins
>can close them out.
>
>
>If OODT is interested in switching over to git and using git-wip-us.a.o
>as the primary repository I would be happy to help migrate them.
>
>
>If you have any other questions let me know
>-Jake
>
>
>
>
>
>
>On Thu, Jan 30, 2014 at 12:21 AM, Chris Mattmann
><[email protected]> wrote:
>
>Thanks Jake. I guess I was under the (potentially) wrong impression
>that we could do pull requests against our Github mirrors for ASF
>projects and they would show up as emails on our
>[email protected] <mailto:[email protected]>
>mailing lists with emails back to the patch that the pull request
>represented. I've seen this in Tika and in a few other projects.
>
>Is that not the case anymore? I could directly commit to OODT as I'm
>a PMC member for the project, but I wanted to be cool and try Github ;)
>
>Cheers,
>Chris
>
>
>
>
>-----Original Message-----
>From: Jake Farrell <[email protected]>
>Reply-To: "[email protected]" <[email protected]>
>Date: Wednesday, January 29, 2014 9:19 PM
>To: jpluser <[email protected]>
>Cc: "[email protected]" <[email protected]>,
>"[email protected]" <[email protected]>
>Subject: Re: OODT's Git mirror at Github is borked
>
>>Hey Chris
>>I have switched the default branch on the Github mirror for OODT to be
>>trunk and closed out the two open pull requests that you had issued. Can
>>you please submit the patches you have to OODT
>> and not issue pull requests against the mirror as no one from OODT will
>>be able to accept/merge them or close the pull request.
>>
>>
>>Thanks
>>-Jake
>>
>>
>>
>>
>>
>>
>>On Wed, Jan 29, 2014 at 11:58 PM, Chris Mattmann
>><[email protected]> wrote:
>>
>>Hey Guys,
>>
>>
>>I just tried to do some Github.com/apache/oodt work and submitted
>>a pull request and saw that the default branch at Github for OODT
>>is the 0.1-incubating branch which in turn seems to have borked
>>my pull request (thinks it's over 800+ changes).
>>
>>Any ideas?
>>
>>Thanks!
>>
>>Cheers,
>>Chris
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>
>
>
>


Reply via email to