Re: [Bioc-devel] git svn dcommit

2016-06-23 Thread Martin Morgan
this has to be done every time you want to sync git to svn. Dan - Original Message - From: "Kasper Daniel Hansen" To: "bioc-devel" Sent: Wednesday, June 22, 2016 6:11:24 PM Subject: [Bioc-devel] git svn dcommit So I have made some updates to minfi and they

Re: [Bioc-devel] git svn dcommit

2016-06-23 Thread Steffen Neumann
ps://bioconductor.org/developers/how-to/git-mirrors/#dealing-wit > > h-prior-history--merge-conflicts > > > > And this has to be done every time you want to sync git to svn. > > > > Dan > > > > > > - Original Message - > > > >

Re: [Bioc-devel] git svn dcommit

2016-06-22 Thread Kasper Daniel Hansen
; To: "bioc-devel" > > Sent: Wednesday, June 22, 2016 6:11:24 PM > > Subject: [Bioc-devel] git svn dcommit > > > So I have made some updates to minfi and they are "safe" in Github. I > now > > want to commit them to Bioconductor. I get pretty

Re: [Bioc-devel] git svn dcommit

2016-06-22 Thread Dan Tenenbaum
l" > Sent: Wednesday, June 22, 2016 6:11:24 PM > Subject: [Bioc-devel] git svn dcommit > So I have made some updates to minfi and they are "safe" in Github. I now > want to commit them to Bioconductor. I get pretty strange results, > although I never really understan

[Bioc-devel] git svn dcommit

2016-06-22 Thread Kasper Daniel Hansen
So I have made some updates to minfi and they are "safe" in Github. I now want to commit them to Bioconductor. I get pretty strange results, although I never really understand what is going on. 1. I clone a fresh copy of minfi from Github. 2. I do # bash update_remotes.sh (using proper path of