On Mon, Oct 01, 2007 at 04:06:09PM -0700, Carl Worth wrote: > Another example is "refs/heads". I avoided this partially by inly > documenting how to push all branches with "--all", but I'd much rather > be able to say that the user could git push URL branch > another-branch..." or "git push URL --all" for convenience. Finally, > git-push itself spews quite a bit of output with "refs/heads" in it > that I don't think is useful at all. For talking with the user, git > should say "branch master" not "refs/heads/master". I'd be nervous about skipping discussion of the refs/ namespace. Sure, introduce branch heads and tags on their own first, but you've got to mention the rest pretty early on. Eventually anyone can find themselves with a tags, heads, and remotes with the same names, and then it's easy to get stuck if you don't have a way to disambiguate. And, really, it doesn't take that much space to explain this stuff. --b. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
