4 ms·
You probably don't. The AOSP is hundreds of individual git repositories. android.kernel.org and the "repo" tool are the only sane way to deal with them.
by rryan 15y ago
You probably don't. The AOSP is hundreds of individual git repositories. android.kernel.org and the "repo" tool are the only sane way to deal with them.
- marcamillion 15y agoOr at least an easy way to browse through the source on the web - rather than having to dload it and have some special tools to allow me to read it. I probably won't be doing anything with it, but very interested to see what it looks like.
- ajross 15y agoSpecial tools in the sense of "shell prompt" and "text editor" you mean? I don't disagree that being able to browse a big source tree on the web is a good thing, and useful in many circumstances. But I continue to be depressed at the level of fear that command line tools elicit in modern developers.
- andrewflnr 15y agoI'm guessing he's referring to the "repo" tool mentioned above.
- ajross 15y agoYou actually don't need repo to check out individual trees; git works fine. And repo is really easy, there are "paste this in" commands on the AOSP site, after which you never need to look at it again if you don't want to (just git pull individual trees).
- there 15y agothere used to be a gitweb running when aosp was hosted at kernel.org. when the repositories were moved to google servers, jbq@ said that a web interface to the repositories will be coming at some point, but it is a lower priority than other things like a gerrit review tool.