[Bioc-devel] Update git-mirrors
Kasper Daniel Hansen
kasperdanielhansen at gmail.com
Fri Jun 17 15:28:03 CEST 2016
What I do, which is not ideal, is to delete my git checkout; re-clone it
from GitHub and run update_remotes.
It is likely these things will change substantially before next release, so
I don't think anyone should spend time fixing this right now.
On Fri, Jun 17, 2016 at 8:50 AM, Thomas Lin Pedersen <thomasp85 at gmail.com>
> 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…
> > On 17 Jun 2016, at 10:58, Elena Grassi <grassi.e at gmail.com> wrote:
> > I manually added the tracking of the release branch picking some piece
> > of code from update_remotes.sh:
> > $ git config --add svn-remote.release-3.3.url
> > $ git config --add svn-remote.release-3.3.fetch
> > :refs/remotes/git-svn-release-3.3
> > $ git fetch bioc
> > remote: Counting objects: 7, done.
> > remote: Total 7 (delta 3), reused 3 (delta 3), pack-reused 4
> > Unpacking objects: 100% (7/7), done.
> > From https://github.com/Bioconductor-mirror/roar
> > 1a892c7..15b5049 master -> bioc/master
> > * [new branch] release-3.3 -> bioc/release-3.3
> > $ git update-ref refs/remotes/git-svn-release-3.3
> > It is not general with variables and so on as long as I was trying to
> > understand the single steps. I suppose that it could be possible to
> > fix update_remotes.sh
> > to deal with the need to simply add a new tracking to the release
> > branch, I could work on it this weekend if no one has already done
> > that and if we think it could
> > be useful.
> > E.
> Bioc-devel at r-project.org mailing list
[[alternative HTML version deleted]]
More information about the Bioc-devel