Scott Chacon <schacon@xxxxxxxxx> writes: > On Fri, Sep 23, 2011 at 12:29 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: >> It just occurred to me that https://github.com/git/git repository might be >> the one you are talking about, but that repository is not even mine. The >> page at https://github.com/git says git@xxxxxxxxxxxxxxxxxx is its contact >> person. >> >> I _suspect_ it is set up to mirror from my k.org repository and obviously >> nothing is updated from that route for the past few weeks. It is correct >> to say "html branch in that repository is no longer updated", but I cannot >> do anything about that repository ;-). > > git/git is a mirror I set up from k.org years ago for git-scm.com. I > believe you've been a collaborator on it for a while now, so you can > push to it if you'd like. The mirroring system is down since k.org > died and I've since moved it off the host I had been using to Heroku, > so I can't do the mirroring that way anymore. If you want to push to > it I'll leave it there, otherwise I'll reroot your repo to be the head > of the GitHub network instead. Ok, to clarify this discussion for people who have been pulling from me and have been wondering where to reset their "origin" to... * I'll start to also push into https://github.com/git/git/ directly, treating it like git://repo.or.cz/alt-git.git/ and other secondary distribution points, that have the integration branches, todo, html and man. * Eventually git://git.kernel.org/pub/scm/git/git.git/ will again start receiving my direct pushes just like it used to. The secondary distribution points will also get my pushes directly (I've made sure with Scott that mirroring into https://github.com/git/git/ from my k.org repository will stay turned off). * https://github.com/gitster/git.git/ will stay a mirror of my private development repository with the topic branches (but without non-source branches like html and mah). I haven't figured out how the preformatted documentation branches will be managed in the longer term, as it seems likely that I no longer would have the post-update hook access to update them upon pushing into my k.org repository. I might end up dropping these branches altogether if it gets too cumbersome for me to maintain, but I do not know yet. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html