Nitesh,
I tried to re-construct the repo starting from what is left in the
SVN repository, but I couldn't get all the branches to come over and it
just generally looks too different to easily replace the bioc repo.
I was thinking though, if its easy for you to clobber the current
bio
Hi Kevin,
I can help you with this. I can take you back to a state before August 18th and
put that repository up on our Git server.
From that point onwards you’d have to reapply all the changes on that
repository from "commit ae93b1e9bcc574b5c8e9fc13b914286464ff4389" and onwards.
commit ae93
Nitesh,
That sounds great, thanks.
Kevin
On 01/03/2018 01:53 PM, Turaga, Nitesh wrote:
Hi Kevin,
I can help you with this. I can take you back to a state before August 18th and
put that repository up on our Git server.
From that point onwards you’d have to reapply all the changes on t
Hi Kevin,
I have your package reset to this commit
e3a8d2122a65305c478276e538faace277ea9ed6.
Please check. You will need to overlay all the commits including the new
release on top of this (RELEASE_3_6).
If you have any questions further on this, please ask before pushing to
Bioconductor.
Hi Kevin,
Please overlay the commits so that we can get your package building on our
build machines.
Please do this soon. You also have to make RELEASE_3_6 branch now.
We have skipped your package for now, and it won’t show up in the release
report.
Thanks
Nitesh
> On Jan 4, 2018, at 10:
Nitesh,
I have pushed changes to both the master and RELEASE_3_6 branches now.
Kevin
On 01/05/2018 11:14 AM, Turaga, Nitesh wrote:
Hi Kevin,
Please overlay the commits so that we can get your package building on our
build machines.
Please do this soon. You also have to make RELEASE_3_6
Hi Kevin,
It seems you have lost a few commits which are important in tracking RELEASE’s
in Bioconductor.
commit fb5868c2fdfa607b52e467881212b3619a8b0ae9 (HEAD -> master)
Author: Hervé Pagès
Date: Mon Oct 30 12:52:08 2017 -0400
bump x.y.z versions to odd y after creation of RELEASE_3_6
Now your version numbers don’t match. You skip versions without those commits
Your history is supposed to look like this,
commit 5a1ad6ff08747d1380875840fe96d3633c210ee2 (HEAD -> master)
Author: khoran
Date: Sun Jan 7 09:44:16 2018 -0800
History was rolled back 6 months to remove dup comm
Hi Kevin,
One last message, give me a green light to fix your repository once you have
had a chance to see my emails.
Best,
Nitesh
> On Jan 7, 2018, at 2:17 PM, Turaga, Nitesh
> wrote:
>
> Now your version numbers don’t match. You skip versions without those commits
>
> Your history is su
Nitesh,
Sorry, just saw your email now. You can go ahead and make those
changes. Thanks for all your help.
Kevin
On 01/07/2018 11:22 AM, Turaga, Nitesh wrote:
Hi Kevin,
One last message, give me a green light to fix your repository once you have
had a chance to see my emails.
Best,
Hi Kevin,
Your repository should now be fixed. Please re-clone your repository.
Best,
Nitesh
> On Jan 8, 2018, at 8:39 PM, Kevin Horan wrote:
>
> Nitesh,
>
>Sorry, just saw your email now. You can go ahead and make those changes.
> Thanks for all your help.
>
> Kevin
>
>
> On 01/07
Nitesh,
I have re-cloned it, everything looks good. Thanks for your help.
Can you please make sure that the duplicate commit check has been
re-enabled for this repo? It was previously disabled.
Kevin
On 01/09/2018 10:03 AM, Turaga, Nitesh wrote:
Hi Kevin,
Your repository should now be
12 matches
Mail list logo
