sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jarek Jarcec Cecho <jar...@apache.org>
Subject Re: Potentially rebase branch-1.99.4
Date Tue, 04 Nov 2014 02:42:57 GMT
I think that it’s acceptable that the release branch-1.99.4 and sqoop2 will have different
commits and in different order - we won’t be merging them them in the future, so as long
as sqoop2 is strict super set of branch-1.99.4, we should be good to go :)

Jarcec

> On Nov 3, 2014, at 2:41 PM, Abraham Elmahrek <abe@cloudera.com> wrote:
> 
> There are a couple. One example is SQOOP-1639.
> 
> On Mon, Nov 3, 2014 at 2:23 PM, Jarek Jarcec Cecho <jarcec@apache.org>
> wrote:
> 
>> I’m wondering what is the issue with different commit other (and different
>> set of commits) between sqoop2 and branch-1.99.4 branches?
>> 
>> Jarcec
>> 
>>> On Nov 3, 2014, at 1:46 PM, Abraham Elmahrek <abe@cloudera.com> wrote:
>>> 
>>> Hey guys,
>>> 
>>> Since sqoop2 branch and branch-1.99.4 may be out of order. I wanted to
>>> check with the community to see if we can rebase to rectify commit order.
>>> This involves:
>>> 1. cherry picking missing commits
>>> 2. Rebasing to change the order
>>> 3. Force pushing on branch-1.99.4
>>> 
>>> -Abe
>> 
>> 


Mime
View raw message