I'll test on mac and windows
cheers, jo
> On 7 Jan 2018, at 22:57, Neumann, Steffen wrote:
>
> Hi,
>
> Following the bug report in
> https://github.com/sneumann/mzR/issues/143
>
> there is a branch with a fix in
> https://github.com/sneumann/mzR/pull/144
>
> that
Hi,
Following the bug report in
https://github.com/sneumann/mzR/issues/143
there is a branch with a fix in
https://github.com/sneumann/mzR/pull/144
that passes Travis in
https://travis-ci.org/sneumann/mzR/builds/324960762
which we can merge once there is a bit more testing
on other
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
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
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
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
Hi Stian,
You cannot push to any branch other than “master” and RELEASE_3_6. Bioconductor
regulates the branches that are available on our GIT server.
You cannot push an additional branch, we recommend you do that on your GitHub,
and merge with master when you are ready, and then push to
7.1.18 12:46, Wolfgang Huber scripsit:
Thank you for your question. It would however be more appropriate for
the support forum, not for the developer mailing list. Would you mind
moving it there, perhaps also the responses so far?
I just saw you posted on the forum, after browsing it.
I had
Dear Julie
Thank you for your question. It would however be more appropriate for
the support forum, not for the developer mailing list. Would you mind
moving it there, perhaps also the responses so far?
There is no "in-principle" reason why DESeq2 shouldn't produce useful
results also for