If you have committed and pushed everything to GitHub, there will be nothing lost by my solution. Just a few minutes of re-cloning.
On Fri, Jun 17, 2016 at 10:02 AM, Elena Grassi <grass...@gmail.com> wrote: > On Fri, Jun 17, 2016 at 2:50 PM, Thomas Lin Pedersen > <thomas...@gmail.com> wrote: > > Thanks for that - for some reason it doesn’t create a local release-3.3 > branch that can be synced to svn? Anyway, I think it’s fair to say that > there need to be some convenient way to update ones git environment after > each Bioconductor release… > > Woops, sorry. I forgot the last command :) > > $ git branch --track svn_release_3.3 bioc/release-3.3 > > E. > p.s. I really wanted to keep my git repo but Kasper's solution also > works if that is not an issue for you :) > > _______________________________________________ > Bioc-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/bioc-devel > [[alternative HTML version deleted]] _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
