Proposal: Gitolite for repository management
Simon Peyton-Jones
simonpj at microsoft.com
Wed Jul 31 18:41:16 CEST 2013
Excellent -- but don't just tell me! Could you add that guidance to the wiki?
Thanks
SImon
| -----Original Message-----
| From: Herbert Valerio Riedel [mailto:hvr at gnu.org]
| Sent: 31 July 2013 10:06
| To: Simon Peyton-Jones
| Cc: Austin Seipp; ghc-devs at haskell.org; Herbert Valerio Riedel
| Subject: Re: Proposal: Gitolite for repository management
|
| On 2013-07-31 at 03:21:48 +0200, Simon Peyton-Jones wrote:
|
| [...]
|
| > * I have lots of check-out repos. Each contains lots of .git/config files
| > because of the multi-repo nature of the GHC build system. It would be
| > a pain to have to edit each individually. Maybe you can tell us a sync-all
| > command to update the URL and pushurl configs, once per tree.
|
| The following should do the trick with the current `./sync-all` for developers:
|
| ./sync-all -r ssh://git@git.haskell.org remote set-url origin
| ./sync-all -r ssh://git@git.haskell.org remote set-url --push origin
|
| Non-authenticated users who have been using only the http:// urls don't
| have to switch right-away (as the old http://darcs.haskell.org uris will
| continue to work), but in the long-term they'll want to update their
| Git urls via
|
| ./sync-all -r http://git.haskell.org remote set-url origin
|
| not the least to benefit from the more efficient Git's smart http
| transport[1] (should we decide to enable that on
| http://git.haskell.org/).
|
| PS: The reason I modification to `sync-all` are mentioned is because it
| contains references to the old Git urls in its emitted help texts.
|
| [1]: http://git-scm.com/blog/2010/03/04/smart-http.html
|
| Cheers,
| hvr
More information about the ghc-devs
mailing list