several steps????

git remote add foo <git-repo-url>
git fetch foo
git checkout -b foo/<branch-witch-patch>
git rebase master
git checkout master
git merge foo/<branch-with-patch>
git push ...


either way, what is the Apache policy on that? Shouldn't each and every code 
snipped be signed of to meet Apache Licence????


mf
Am 12.02.2014 um 21:44 schrieb Martin Grigorov <[email protected]>:

> On Wed, Feb 12, 2014 at 7:12 PM, Martin Funk <[email protected]> wrote:
> 
>>> Pull Requests are still not supported.
>> But they could be pulled to local and then pushed to the apache repo by
>> core commiters, right?
>> 
> 
> Right, but it involves "manual" work in several steps.
> For me the easiest way is to add '.patch' to the PR url, download it and
> 'git am' it. This losses the author info though...
> 
> 
>> 
>> mf
>> 
>> Am 12.02.2014 um 09:52 schrieb Martin Grigorov <[email protected]>:
>> 
>>> Don't get too excited :)
>>> It is just about mail notifications and comments in JIRA/GitHub.
>>> Pull Requests are still not supported.
>>> 
>>> Martin Grigorov
>>> Wicket Training and Consulting
>>> 
>>> 
>>> On Wed, Feb 12, 2014 at 9:48 AM, Santo Raso <[email protected]> wrote:
>>> 
>>>> Finally!!!!
>>>> 
>>>> 
>>>> 2014-02-12 9:00 GMT+01:00 Jeremy Thomerson <[email protected]>:
>>>> 
>>>>> Yes!
>>>>> 
>>>>> 
>>>>> On Wed, Feb 12, 2014 at 2:18 AM, Martin Grigorov <[email protected]
>>>>>> wrote:
>>>>> 
>>>>>> Hi,
>>>>>> 
>>>>>> Just noticed
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
>>>>>> 
>>>>>> We want all of it, right ?!
>>>>>> 
>>>>>> Martin Grigorov
>>>>>> Wicket Training and Consulting
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Jeremy Thomerson
>>>>> http://wickettraining.com
>>>>> 
>>>> 
>> 
>> 

Reply via email to