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 16:16:00 UTC
Re: Branch v0.3.0 created (CORRECTION)
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>.
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.