I finally got to the bottom of my issue. It's the ' color.branch' variable that causes the trouble for the bash script. Because I had explicitly set it to 'always' in my '~/.gitconfig' file, `git branch -r ` command append the wierd control characters to the release branch name, e.g. 'release-3.0^[[m', which messed up the 'svn-remote' subsection within '.git/config' file. After I changed this variable value to 'auto', the script runs successfully now.
Thanks a lot! On 06/19/2015 12:25 PM, Jim Hester wrote: > Mike, > > We are unable to reproduce this issue using the commands provided. > Maybe try starting over from scratch and see if it works, perhaps > there was a network error the first time you tried it? > > Jim > > On Fri, Jun 19, 2015 at 3:03 PM, Mike <wjia...@fhcrc.org > <mailto:wjia...@fhcrc.org>> wrote: > > I am having trouble to set up the remote. > > git clone https://github.com/RGLab/flowQ > cd flowQ/ > git branch -a > * master > remotes/origin/HEAD -> origin/master > remotes/origin/master > curl -O > > https://raw.githubusercontent.com/Bioconductor/mirror/master/update_remotes.sh > bash update_remotes.sh > fatal: refs/remotes/bioc/release-3.0: not a valid SHA1 > > Mike > > > _______________________________________________ > Bioc-devel@r-project.org <mailto: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