On Fri, Oct 22, 2010 at 9:53 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Sitaram Chamarty <sitaramc@xxxxxxxxx> writes: > >> Subject line says it all... While working with people trying to use >> gitolite's new support for the "smart HTTP" mode, I find sometimes >> they get side-tracked by this document. > > Not everybody uses gitolite, and I do not think we have broken the dumb > HTTP support (however broken the original was ;-) to render the document > obsolete. My apologies; I didn't realise my mail would come across like that. Let me clarify. "While working with gitolite users" was only meant to explain how *I* came across the issue, nothing more. I assumed that the new -- much more efficient (correct?) transport would make the older (dumber) transport obsolete, and I didn't realise it had any advantages over the new one. > Perhaps we should do three and half things: > > Â- The said documentation should be fine as is if the reader is trying to > Â set up a dumb HTTP push support; otherwise it should be updated. > > Â- It would be really nice if somebody wrote a similar document describing > Â how to set up a smart HTTP server, and put it next to the said > Â documentation. I just followed "man git-http-backend" and it all worked. Should there be more? > Â- When the above two is done, insert one line "This describes an older > Â way; see <<insert the name of the other document here>> for insn to set > Â up an experimental smart HTTP server" at the beginning of the original > Â document. > > and finally: > > Â- On the gitolite side, refer to the "new" document in git.git > Â documentation set. It does refer to the new one, otherwise no one would have been able to use those instructions! Just that some people... I don't know.. gloss over the exact filename maybe... or they find the other one first and think it's the right one... Anyway, you're partly right -- I probably should highlight it better in my docs. Thanks -- Sitaram -- 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