Hello,
Systems team recently made some cleanups and elaborations to Linaro git
services, information about which we'd like to share here. None of
these changes require immediate changes on your side (compatibility
with old usage ways is kept), but we'd like to draw some attention to
them anyway, as they should make life a bit easier, especially for
newstarters, so it would be nice if people were aware of them and not
pass old information around.
1. To access gitolite push services, "git" user is now used
consistently across various hosts. (Previously, it was "git" for the
main server, git.linaro.org, but various other names on team- and
project-specific servers). Old names are kept for compatibility, but
you will see "git@" in gitweb, and that's the preferred way to pass
links to other people.
2. Our initial instructions for git services included steps of update
user's SSH config in ~/.ssh/config. Based on the experience, we found
that lead to confusion and surprises (for example, if you switched
workstation or resetup one from scratch). So, this usage is
deprecated now - instead, SSH repo URLs should contain explicit
username ("git@", per above). Instructions were updated
correspondingly. You can keep using your existing SSH config and
cloned repos, just please pass fully specified clone URLs to other
people.
Summing up:
You can look up authoritative access URLs for a repo in gitweb. E.g.:
https://git.linaro.org/boot/u-boot-linaro-next.git . If you need to
pass git clone info to other people, please use what's written
there (giving gitweb URL is probably the easiest).
You don't need to change anything on your side.
--
Best Regards,
Paul
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
