[Bioc-devel] cherry picking fixes to release

Sun, Dec 3, 2017 10:18 AM #

Was the website ever updated for this? I don't see the

git checkout -b <RELEASE_X_Y> upstream/<RELEASE_X_Y>

which has to be done the first time patching a release.

On Tue, Oct 3, 2017 at 11:19 AM, Turaga, Nitesh <

Nitesh.Turaga at roswellpark.org> wrote:

Thanks for the heads up. I will fix the documentation on the website.

Best,

Nitesh

On Oct 3, 2017, at 2:17 PM, Michael Lawrence <lawrence.michael at gene.com>

wrote:

Yes, that seems to have fixed it. Thanks for your help.

I guess the guide on the Bioc website needs to be tweaked.

Michael

On Tue, Oct 3, 2017 at 11:15 AM, Turaga, Nitesh
<Nitesh.Turaga at roswellpark.org> wrote:

I?m just guessing, but I think ?git? is trying to work on the upstream

RELEASE_3_5 directly.

Maybe try,

       git fetch ?all
       git checkout -b RELASE_3_5 upstream/RELEASE_3_5   ## This will

create a local branch RELEASE_3_5 which follows your upstream/RELEASE_3_5

This should not have that detached head state.

Nitesh

On Oct 3, 2017, at 2:11 PM, Turaga, Nitesh

<Nitesh.Turaga at RoswellPark.org> wrote:

Hi Micheal,

This is very interesting, I?m never run across it.

Can you tell me what package you are working on, and I?ll try your

commands as a user. (I won?t push anything, just want to reproduce the
error)

Best,

Nitesh

On Oct 3, 2017, at 1:51 PM, Michael Lawrence <

lawrence.michael at gene.com> wrote:

Hi Nitesh,

I tried following your guide to fixing bugs in devel and release, but
I hit a hurdle.

I did a git fetch --all. Then a git branch RELEASE_3_5.

But I end up in a weird detached head state.

bash-3.2$ git branch
* (HEAD detached from origin/RELEASE_3_5)
master

Do you have any ideas?

Thanks,
Michael



This email message may contain legally privileged and/or confidential

information.  If you are not the intended recipient(s), or the employee or
agent responsible for the delivery of this message to the intended
recipient(s), you are hereby notified that any disclosure, copying,
distribution, or use of this email message is prohibited.  If you have
received this message in error, please notify the sender immediately by
e-mail and delete this email message from your computer. Thank you.



This email message may contain legally privileged and/or confidential
information.  If you are not the intended recipient(s), or the employee or
agent responsible for the delivery of this message to the intended
recipient(s), you are hereby notified that any disclosure, copying,
distribution, or use of this email message is prohibited.  If you have
received this message in error, please notify the sender immediately by
e-mail and delete this email message from your computer. Thank you.

Turaga, Nitesh

Mon, Dec 4, 2017 5:56 AM #

Hi Michael, 

Thanks for catching this. It is updated now.

Best

On Dec 3, 2017, at 1:18 PM, Michael Lawrence <lawrence.michael at gene.com> wrote:

Was the website ever updated for this? I don't see the 

git checkout -b <RELEASE_X_Y> upstream/<RELEASE_X_Y>

which has to be done the first time patching a release.

On Tue, Oct 3, 2017 at 11:19 AM, Turaga, Nitesh <Nitesh.Turaga at roswellpark.org> wrote:
Thanks for the heads up. I will fix the documentation on the website.

Best,

Nitesh

On Oct 3, 2017, at 2:17 PM, Michael Lawrence <lawrence.michael at gene.com> wrote:

Yes, that seems to have fixed it. Thanks for your help.

I guess the guide on the Bioc website needs to be tweaked.

Michael

On Tue, Oct 3, 2017 at 11:15 AM, Turaga, Nitesh
<Nitesh.Turaga at roswellpark.org> wrote:

I?m just guessing, but I think ?git? is trying to work on the upstream RELEASE_3_5 directly.

Maybe try,

       git fetch ?all
       git checkout -b RELASE_3_5 upstream/RELEASE_3_5   ## This will create a local branch RELEASE_3_5 which follows your upstream/RELEASE_3_5

This should not have that detached head state.

Nitesh

On Oct 3, 2017, at 2:11 PM, Turaga, Nitesh <Nitesh.Turaga at RoswellPark.org> wrote:

Hi Micheal,

This is very interesting, I?m never run across it.

Can you tell me what package you are working on, and I?ll try your commands as a user. (I won?t push anything, just want to reproduce the error)

Best,

Nitesh

On Oct 3, 2017, at 1:51 PM, Michael Lawrence <lawrence.michael at gene.com> wrote:

Hi Nitesh,

I tried following your guide to fixing bugs in devel and release, but
I hit a hurdle.

I did a git fetch --all. Then a git branch RELEASE_3_5.

But I end up in a weird detached head state.

bash-3.2$ git branch
* (HEAD detached from origin/RELEASE_3_5)
master

Do you have any ideas?

Thanks,
Michael



This email message may contain legally privileged and/or confidential information.  If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited.  If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.



This email message may contain legally privileged and/or confidential information.  If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited.  If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.

This email message may contain legally privileged and/or confidential information.  If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited.  If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.