While testing recent http-fetch changes with a current checkout of next, I noticed a couple of things: - "git push" seems to pass --thin by default to http-push, which subsequently barfs because that's not a valid http-push option. Should it be? Should it be silently ignored? Should git-push not default to --thin when pushing with HTTP transport? - when I clone, http-fetch outputs a whole bunch of "error: Could not read ..." messages - is that expected? -- For a successful technology, reality must take precedence over public relations, for nature cannot be fooled. - : 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