right? Now, suppose I make a bug fix and commit to the
>>> release repository and I want the same fix in the development repository
>>> as
>>> well, how exactly do I go about this: Do I just manually copy those files
>>> with the changes to the other development
ould
mean I need to maintain three projects in R-Studio, right?) Or is there any
other way about this?
Thanks,
Mani
From: Gabe Becker [mailto:becker.g...@gene.com]
Sent: Saturday, October 15, 2016 4:35 PM
To: Kasper Daniel Hansen
Cc: S Manimaran; bioc-devel@r-project.org
Subject: Re: [Bioc-dev
t; other way about this?
>
>
>
> Thanks,
>
> Mani
>
>
>
>
> From: Gabe Becker [mailto:becker.g...@gene.com]
> Sent: Saturday, October 15, 2016 4:35 PM
> To: Kasper Daniel Hansen
> Cc: S Manimaran; bioc-devel@r-project.org
> Subject: Re: [Bioc-devel] Git
Mani,
Related to what Kasper said, one thing you can do is commit directly to the
canonical repo for your package (which again is not on github once the
package is accepted) from rstudio. It supports svn.
~G
On Oct 15, 2016 11:38 AM, "Kasper Daniel Hansen" <
kasperdanielhan...@gmail.com> wrote:
Not at the moment. We are in the (long) process of changing this, but
there is no ETA for it.
The complications we currently have, as soon as a package is accepted in
Bioconductor, is that the "true" repository then becomes Bioconductor SVN
and your Github repository is just a way for you to deve
