Re: Managing git remotes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am So den 6. Mär 2016 um 18:06 schrieb Christopher Baines: > just fixup?), so it does not really work. I also want 2 standard remotes > for most of the repositories, but that would require adding different > fixup lines to all of repository definitions. Well, Maybe not for the past, but why don't you use git url..insteadOf feature? That allows you to use kind of alias for your Repos and if they change, just change the alias. I used to have short alias for my main repositories. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCgAGBQJW3VGfAAoJEKZ8CrGAGfasDSsL+wWV5qotEBQU1hOc98PeudcG UhJ/DXuTVVgnqeopyXFXffkwuxr97fLsVQk9MS8l6T7TigPCKUVDAqxjIKq8dsUB nXQzkU0Mo1s9NznGLnyyq8/CMQ6ZfuwR/weGaFpFMGOk30GPtJoZdMWL0Klu90R+ MlPl2aDtrU3WRsZcTlqoWafmlqv2jUJWYr6ANMnJvrfCxP8ebTswLXk3eCDZN3dT ZE4nM+X345+o6HQRyjoZJMy+/IEeL1a2bPKvjD9BNGGwEXBoZXKvPfLGC2XIUQoF sGzmAWdrn1x3l3DNKslRkyVrRkUsK+CuyQScAcQiA626UKI8JJN/ZFr+2P00dVHB zUyCqhK9FCLA2pi2dma1UXKN/cu9qtXmrOFg79QaGcA6ujMpb3rfhYRtDehJuacn rZJgyqu2MWal+gtE8MdIDPd38cvaWVVxmcTj4AS6HK2kLtBAgcFrElU3Re4rxFoY /Ng3K2HozlCe33j9AN2hdJyV8okoEn52ZjDzHvvsJQ== =m5eM -END PGP SIGNATURE- ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: Managing git remotes
Christopher Baines wrote: > The issues I am having here seem to be around managing the git remotes > in a large number of repositories, so I'm sending a quick email to see > if anyone is also having this issue, and/or if anyone has some > tips/solutions for dealing with this? If I understand correctly, you should be able to do this with either the new-ish `vcsh foreach` command, or perhaps `mr run`. vcsh foreach will run the specified git command (w/ args) in the context of each repo, and can be particularly handy for issues like this. Using this approach, write a script that updates the remote(s) in each repo as needed. Small scripts can just be aliases in .gitconfig. See examples at [1]. More interesting scripts can be named using the pattern "git-" and stuck somewhere on your PATH. Then you can run `vcsh foreach [args…]` to fixup your remotes en masse. Cheers, John [1] https://github.com/jwhitley/dotfiles/blob/master/.gitconfig ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Managing git remotes
So I have ~60 git repositories that I manage with the help of mr and vcsh. Recently though, the main server that I used as a git remote (running gitolite) failed, and I switched to another. This worked fine, apart from all the repositories are now configured to point at the old (non-existent server). I tried using the fixups mr configuration to setup the proper remotes in the repository, but this does not run if update fails (is there a way to just fixup?), so it does not really work. I also want 2 standard remotes for most of the repositories, but that would require adding different fixup lines to all of repository definitions. The issues I am having here seem to be around managing the git remotes in a large number of repositories, so I'm sending a quick email to see if anyone is also having this issue, and/or if anyone has some tips/solutions for dealing with this? Thanks, Chris signature.asc Description: OpenPGP digital signature ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
