You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by Kevin Minder <ke...@hortonworks.com> on 2013/10/01 15:44:29 UTC
Branch v0.3.0 created
Hi Everyone,
I just created the v0.3.0 branch. Any changes targeted for v0.3.0 must
now be "double pushed" into master and v0.3.0 branches. Hopefully this
won't be many.
You can checkout and work on the new branch via this command.
git checkout -b v0.3.0
The easiest way to move changes between branches is probably by creating
a patch in one and then applying it in the other. I'm sure there are
better ways using git. I'm open for suggestions.
Kevin.
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Branch v0.3.0 created
Posted by Sergey Balan CV <sb...@hortonworks.com>.
Yes. You are right.
On Tue, Oct 1, 2013 at 5:15 PM, Kevin Minder
<ke...@hortonworks.com>wrote:
> Sergey,
> I think you need to wait until I have a Jenkins job setup to build the
> RPM. Please correct me if I'm wrong.
> Kevin.
>
>
> On 10/1/13 10:10 AM, Sergey Balan CV wrote:
>
>> Hi Kevin,
>>
>> Can I modify BigTop + Knox integration now?
>> Or should I wait for update from Ashish?
>>
>> Thanks, Sergey.
>>
>>
>> On Tue, Oct 1, 2013 at 4:45 PM, Kevin Minder
>> <ke...@hortonworks.com>**wrote:
>>
>> Just wanted to mention that the svn site repo will not be branched. I
>>> think we should continue to operate on the trunk there.
>>>
>>>
>>> On 10/1/13 9:44 AM, Kevin Minder wrote:
>>>
>>> Hi Everyone,
>>>>
>>>> I just created the v0.3.0 branch. Any changes targeted for v0.3.0 must
>>>> now be "double pushed" into master and v0.3.0 branches. Hopefully this
>>>> won't be many.
>>>>
>>>> You can checkout and work on the new branch via this command.
>>>>
>>>> git checkout -b v0.3.0
>>>>
>>>> The easiest way to move changes between branches is probably by creating
>>>> a patch in one and then applying it in the other. I'm sure there are
>>>> better ways using git. I'm open for suggestions.
>>>>
>>>> Kevin.
>>>>
>>>>
>>> --
>>> CONFIDENTIALITY NOTICE
>>> NOTICE: This message is intended for the use of the individual or entity
>>> to which it is addressed and may contain information that is
>>> confidential,
>>> privileged and exempt from disclosure under applicable law. If the reader
>>> of this message is not the intended recipient, you are hereby notified
>>> that
>>> any printing, copying, dissemination, distribution, disclosure or
>>> forwarding of this communication is strictly prohibited. If you have
>>> received this communication in error, please contact the sender
>>> immediately
>>> and delete it from your system. Thank You.
>>>
>>>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity
> to which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Branch v0.3.0 created
Posted by Kevin Minder <ke...@hortonworks.com>.
Sergey,
I think you need to wait until I have a Jenkins job setup to build the
RPM. Please correct me if I'm wrong.
Kevin.
On 10/1/13 10:10 AM, Sergey Balan CV wrote:
> Hi Kevin,
>
> Can I modify BigTop + Knox integration now?
> Or should I wait for update from Ashish?
>
> Thanks, Sergey.
>
>
> On Tue, Oct 1, 2013 at 4:45 PM, Kevin Minder
> <ke...@hortonworks.com>wrote:
>
>> Just wanted to mention that the svn site repo will not be branched. I
>> think we should continue to operate on the trunk there.
>>
>>
>> On 10/1/13 9:44 AM, Kevin Minder wrote:
>>
>>> Hi Everyone,
>>>
>>> I just created the v0.3.0 branch. Any changes targeted for v0.3.0 must
>>> now be "double pushed" into master and v0.3.0 branches. Hopefully this
>>> won't be many.
>>>
>>> You can checkout and work on the new branch via this command.
>>>
>>> git checkout -b v0.3.0
>>>
>>> The easiest way to move changes between branches is probably by creating
>>> a patch in one and then applying it in the other. I'm sure there are
>>> better ways using git. I'm open for suggestions.
>>>
>>> Kevin.
>>>
>>
>> --
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity
>> to which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender immediately
>> and delete it from your system. Thank You.
>>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Branch v0.3.0 created
Posted by Sergey Balan CV <sb...@hortonworks.com>.
Hi Kevin,
Can I modify BigTop + Knox integration now?
Or should I wait for update from Ashish?
Thanks, Sergey.
On Tue, Oct 1, 2013 at 4:45 PM, Kevin Minder
<ke...@hortonworks.com>wrote:
> Just wanted to mention that the svn site repo will not be branched. I
> think we should continue to operate on the trunk there.
>
>
> On 10/1/13 9:44 AM, Kevin Minder wrote:
>
>> Hi Everyone,
>>
>> I just created the v0.3.0 branch. Any changes targeted for v0.3.0 must
>> now be "double pushed" into master and v0.3.0 branches. Hopefully this
>> won't be many.
>>
>> You can checkout and work on the new branch via this command.
>>
>> git checkout -b v0.3.0
>>
>> The easiest way to move changes between branches is probably by creating
>> a patch in one and then applying it in the other. I'm sure there are
>> better ways using git. I'm open for suggestions.
>>
>> Kevin.
>>
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity
> to which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Branch v0.3.0 created
Posted by Kevin Minder <ke...@hortonworks.com>.
Just wanted to mention that the svn site repo will not be branched. I
think we should continue to operate on the trunk there.
On 10/1/13 9:44 AM, Kevin Minder wrote:
> Hi Everyone,
>
> I just created the v0.3.0 branch. Any changes targeted for v0.3.0
> must now be "double pushed" into master and v0.3.0 branches. Hopefully
> this won't be many.
>
> You can checkout and work on the new branch via this command.
>
> git checkout -b v0.3.0
>
> The easiest way to move changes between branches is probably by
> creating a patch in one and then applying it in the other. I'm sure
> there are better ways using git. I'm open for suggestions.
>
> Kevin.
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Branch v0.3.0 created (CORRECTION)
Posted by Kevin Minder <ke...@hortonworks.com>.
OK the right command might actually be
git checkout -t origin/v0.3.0
Gotta love git!
On 10/1/13 10:16 AM, Kevin Minder wrote:
> Correction. It looks like this command is required to properly track
> the remote branch.
>
> git checkout -tb v0.3.0
>
> On 10/1/13 9:44 AM, Kevin Minder wrote:
>> Hi Everyone,
>>
>> I just created the v0.3.0 branch. Any changes targeted for v0.3.0
>> must now be "double pushed" into master and v0.3.0 branches.
>> Hopefully this won't be many.
>>
>> You can checkout and work on the new branch via this command.
>>
>> git checkout -b v0.3.0
>>
>> The easiest way to move changes between branches is probably by
>> creating a patch in one and then applying it in the other. I'm sure
>> there are better ways using git. I'm open for suggestions.
>>
>> Kevin.
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Branch v0.3.0 created (CORRECTION)
Posted by Kevin Minder <ke...@hortonworks.com>.
Correction. It looks like this command is required to properly track
the remote branch.
git checkout -tb v0.3.0
On 10/1/13 9:44 AM, Kevin Minder wrote:
> Hi Everyone,
>
> I just created the v0.3.0 branch. Any changes targeted for v0.3.0
> must now be "double pushed" into master and v0.3.0 branches. Hopefully
> this won't be many.
>
> You can checkout and work on the new branch via this command.
>
> git checkout -b v0.3.0
>
> The easiest way to move changes between branches is probably by
> creating a patch in one and then applying it in the other. I'm sure
> there are better ways using git. I'm open for suggestions.
>
> Kevin.
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.