-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In your git config, you can define a pushurl that is different from url. Which effectively means that you can pull from github but push to tor.
So in .git/config, your entry would look something like this (double-check pushurl syntax): [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = g...@github.com:zackw/stegotorus.git fetch = +refs/heads/*:refs/remotes/origin/* pushurl = za...@gitweb.torproject.org/stegotorus.git [branch "master"] remote = origin merge = refs/heads/master You could also clone to new directory, change the origin to tor, then push each branch. Unless there are just tons of branches, this should only take a couple of minutes =) best, Griffin On 04/01/2014 11:01 AM, Zack Weinberg wrote: > On 02/20/2014 10:48 AM, vmonmoonsh...@gmail.com wrote: >> Hey Zack, >> >> I want to put up Stegotorus up for GSoC this summer. I was >> wondering if you mind transfering the ownership of your >> Stegotorus repo: >> >> https://github.com/zackw/stegotorus >> >> To "TheTorProject" on github: >> >> https://github.com/TheTorProject >> >> ? (https://github.com/zackw/stegotorus/settings then Transfer) >> >> If you don't feel comfortable, we can fork it as well. > > [ Background for tor-dev: I am no longer involved in Stegotorus > development. vmon and at least one other person are continuing to > work on it; this is currently happening in non-default branches of > the copy on my github account. There is also a copy of the repo > on gitweb.torproject.org but it has not been updated in quite some > time. ] > > I discussed this with Roger on IRC yesterday and we came to the > conclusion that instead of transferring my Stegotorus repo to the > "TheTorProject" organizational account, > gitweb.torproject.org/stegotorus.git should be promoted to the > master copy. I think right now I am the only person with write > access to that copy, and I am not sure what the right procedure is > for granting you access. I'm also not good enough at Git to know > how to copy all branches of remote A into remote B (short of > tedious manual actions and/or shell loops). > > I think this would also entail using Tor's Trac for issues instead > of Github's issue tracker. > > zw > > > > _______________________________________________ tor-dev mailing > list tor-dev@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTOtnhAAoJEAPPSgqzx5pjlKgH/AmLj3tHAOPg3VvJaDHAt/Nh ZesH9vJrF2ZdipJhK0QTXnOHsdk5nIxNlnNC/VRLv09At7mzu4X5l9ZvECLlj64f JeQVhHJ4lFj141mc1LabBnGoppYHOssBMS2HZH0ef8pEGyOJwhacYILDuzIfmn1A Zs21V9EKd6WIIyyLtnA5BNNZmMHWSCqVSxbXDMM3Sk8lRupYzD2FF4D6xkdlqW3A WKMBLTA0MTOVDkmJVYv0e65A05hFOv6Fxh/YF41HrgIhjulv6fdK50Y5pFqaKuv6 BU1hU3n80rWPnLjezUj8a/cd2ZliXUVMElAnyoVd41Nprfem2XuJMT3UmgShydQ= =Kdkg -----END PGP SIGNATURE----- _______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev