managing remotes collaboratively with mr

Yaroslav Halchenko lists at
Sat Apr 30 02:15:31 CEST 2011

just my 0.1 cents since now it is not recommended way per se since iirc
mr got proper actions (RTFM ;-) ) to be defined to run for such purposes, but
for one of the projects I have done following:

lib =
    export NIPY=git://
    git_assure_remote() {
        git remote | grep -q "^$remote$" || {
            echo I: Adding remote $remote
            git remote add "$remote" "$url"
            git fetch "$remote"
    git_assure_gh_clones() {
        # Since all clones on github are uniformly organized
        # we can shortcut it
        for login in $*; do
            git_assure_remote $login git://$login/$project.git

checkout = git clone "${NIPY}/nibabel.git"
update =
       git_assure_gh_clones nibabel hanke matthew-brett


On Fri, 29 Apr 2011, micah anderson wrote:
> But what if someone adds a new remote? Because I put things in the
> .mrconfig as a 'post_checkout' the new remote will not be added to the
> git repository. I could add the remotes twice, in a post_checkout (for
> the new person who wants to get them all) and then also as a pre_update,
> but that seems a bit ugly.

> Thanks for any ideas, or better ways to do this!
> micah
Keep in touch                           
Yaroslav Halchenko       

More information about the vcs-home mailing list