{"thread":{"id":"25513","subject":"should Documentation/howto/setup-git-server-over-http.txt be marked obsolete?","startedAt":"2010-10-22T03:48:32Z","lastAt":"2010-10-23T07:24:50Z","messageCount":8,"participants":["Sitaram Chamarty","Junio C Hamano","Jonathan Nieder","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"154090","messageId":"AANLkTimJe9vEUwWM482NLmfHGYjnsKD5RAryQO=Zyqjj@mail.gmail.com","threadId":"25513","inReplyTo":null,"subject":"should Documentation/howto/setup-git-server-over-http.txt be marked obsolete?","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2010-10-22T03:48:32Z","receivedAt":"2010-10-22T03:48:32Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"Subject line says it all... While working with people trying to use\ngitolite's new support for the \"smart HTTP\" mode, I find sometimes\nthey get side-tracked by this document.\n\nIs there any text we could add to it to say \"ok guys this is from\n2006, a lot has happened in git since those days...\" etc?\n\nthanks,\n\n-- \nSitaram\n"},{"id":"154095","messageId":"7vsjzyrh2w.fsf@alter.siamese.dyndns.org","threadId":"25513","inReplyTo":"AANLkTimJe9vEUwWM482NLmfHGYjnsKD5RAryQO=Zyqjj@mail.gmail.com","subject":"Re: should Documentation/howto/setup-git-server-over-http.txt be marked obsolete?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2010-10-22T04:23:35Z","receivedAt":"2010-10-22T04:23:35Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Sitaram Chamarty <sitaramc@gmail.com> writes:\n\n> Subject line says it all... While working with people trying to use\n> gitolite's new support for the \"smart HTTP\" mode, I find sometimes\n> they get side-tracked by this document.\n\nNot everybody uses gitolite, and I do not think we have broken the dumb\nHTTP support (however broken the original was ;-) to render the document\nobsolete.\n\nPerhaps we should do three and half things:\n\n - The said documentation should be fine as is if the reader is trying to\n   set up a dumb HTTP push support; otherwise it should be updated.\n\n - It would be really nice if somebody wrote a similar document describing\n   how to set up a smart HTTP server, and put it next to the said\n   documentation.\n\n - When the above two is done, insert one line \"This describes an older\n   way; see <<insert the name of the other document here>> for insn to set\n   up an experimental smart HTTP server\" at the beginning of the original\n   document.\n\nand finally:\n\n - On the gitolite side, refer to the \"new\" document in git.git\n   documentation set.\n"},{"id":"154145","messageId":"AANLkTinv3kzvtC_Pq4F0cM_JqU7-Q2a=sWs8YSxbMiPs@mail.gmail.com","threadId":"25513","inReplyTo":"7vsjzyrh2w.fsf@alter.siamese.dyndns.org","subject":"Re: should Documentation/howto/setup-git-server-over-http.txt be marked obsolete?","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2010-10-22T13:55:31Z","receivedAt":"2010-10-22T13:55:31Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On Fri, Oct 22, 2010 at 9:53 AM, Junio C Hamano <gitster@pobox.com> wrote:\n> Sitaram Chamarty <sitaramc@gmail.com> writes:\n>\n>> Subject line says it all... While working with people trying to use\n>> gitolite's new support for the \"smart HTTP\" mode, I find sometimes\n>> they get side-tracked by this document.\n>\n> Not everybody uses gitolite, and I do not think we have broken the dumb\n> HTTP support (however broken the original was ;-) to render the document\n> obsolete.\n\nMy apologies; I didn't realise my mail would come across like that.\n\nLet me clarify.  \"While working with gitolite users\" was only meant to\nexplain how *I* came across the issue, nothing more.\n\nI assumed that the new -- much more efficient (correct?) transport\nwould make the older (dumber) transport obsolete, and I didn't realise\nit had any advantages over the new one.\n\n> Perhaps we should do three and half things:\n>\n>  - The said documentation should be fine as is if the reader is trying to\n>   set up a dumb HTTP push support; otherwise it should be updated.\n>\n>  - It would be really nice if somebody wrote a similar document describing\n>   how to set up a smart HTTP server, and put it next to the said\n>   documentation.\n\nI just followed \"man git-http-backend\" and it all worked.  Should there be more?\n\n>  - When the above two is done, insert one line \"This describes an older\n>   way; see <<insert the name of the other document here>> for insn to set\n>   up an experimental smart HTTP server\" at the beginning of the original\n>   document.\n>\n> and finally:\n>\n>  - On the gitolite side, refer to the \"new\" document in git.git\n>   documentation set.\n\nIt does refer to the new one, otherwise no one would have been able to\nuse those instructions!\n\nJust that some people... I don't know.. gloss over the exact filename\nmaybe... or they find the other one first and think it's the right\none...\n\nAnyway, you're partly right -- I probably should highlight it better in my docs.\n\nThanks\n\n-- \nSitaram\n"},{"id":"154152","messageId":"20101022150627.GB9224@burratino","threadId":"25513","inReplyTo":"AANLkTinv3kzvtC_Pq4F0cM_JqU7-Q2a=sWs8YSxbMiPs@mail.gmail.com","subject":"Re: should Documentation/howto/setup-git-server-over-http.txt be marked obsolete?","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2010-10-22T15:06:27Z","receivedAt":"2010-10-22T15:06:27Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Sitaram Chamarty wrote:\n\n> I assumed that the new -- much more efficient (correct?) transport\n> would make the older (dumber) transport obsolete, and I didn't realise\n> it had any advantages over the new one.\n\nFWIW the old transport still has its place.  If your web host (e.g.,\nan ISP) allows only static content (no CGI), then there is no choice.\n\nNot so relevant for gitolite but still relevant in the world.\n\nHope that helps,\nJonathan\n"},{"id":"154183","messageId":"7viq0um5vt.fsf@alter.siamese.dyndns.org","threadId":"25513","inReplyTo":"AANLkTinv3kzvtC_Pq4F0cM_JqU7-Q2a=sWs8YSxbMiPs@mail.gmail.com","subject":"Re: should Documentation/howto/setup-git-server-over-http.txt be marked obsolete?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2010-10-22T18:36:38Z","receivedAt":"2010-10-22T18:36:38Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Sitaram Chamarty <sitaramc@gmail.com> writes:\n\n>> Not everybody uses gitolite, and I do not think we have broken the dumb\n>> HTTP support (however broken the original was ;-) to render the document\n>> obsolete.\n>\n> My apologies; I didn't realise my mail would come across like that.\n\nOh no need for that; I didn't realise -my- response would, either ;-)\n\n> I just followed \"man git-http-backend\" and it all worked.  Should there be more?\n\nNo; that would mean the next step would be (as you suggested)...\n\n>>  - When the above two is done, insert one line \"This describes an older\n>>   way; see <<insert the name of the other document here>> for insn to set\n>>   up an experimental smart HTTP server\" at the beginning of the original\n>>   document.\n\n... this one.\n\nI trust you can take care of the gitolite documentation side ;-)\n\nThanks.\n"},{"id":"154229","messageId":"AANLkTimTVviTBfY1Zeebyhufr36U+0w7VYf4f=25FMFi@mail.gmail.com","threadId":"25513","inReplyTo":"20101022150627.GB9224@burratino","subject":"Re: should Documentation/howto/setup-git-server-over-http.txt be marked obsolete?","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2010-10-23T06:27:31Z","receivedAt":"2010-10-23T06:27:31Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On Fri, Oct 22, 2010 at 8:36 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:\n> Sitaram Chamarty wrote:\n>\n>> I assumed that the new -- much more efficient (correct?) transport\n>> would make the older (dumber) transport obsolete, and I didn't realise\n>> it had any advantages over the new one.\n>\n> FWIW the old transport still has its place.  If your web host (e.g.,\n> an ISP) allows only static content (no CGI), then there is no choice.\n>\n> Not so relevant for gitolite but still relevant in the world.\n\nAlso I now realise the new transport requires Apache, so people with\nother web servers probably need it too.\n\nI guess what remains is that the protocol is not efficient enough,\nespecially for normal push/fetch working-day interactions.  I'll find\nsuitable wording that reflects all this...\n\nthanks\n\nsitaram\n"},{"id":"154230","messageId":"AANLkTi=mP6r=QSLs-rVv3H1PKpwA3NQZW90Nwn1Zu3V6@mail.gmail.com","threadId":"25513","inReplyTo":"7viq0um5vt.fsf@alter.siamese.dyndns.org","subject":"Re: should Documentation/howto/setup-git-server-over-http.txt be marked obsolete?","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2010-10-23T06:29:00Z","receivedAt":"2010-10-23T06:29:00Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On Sat, Oct 23, 2010 at 12:06 AM, Junio C Hamano <gitster@pobox.com> wrote:\n\n> No; that would mean the next step would be (as you suggested)...\n>\n>>>  - When the above two is done, insert one line \"This describes an older\n>>>   way; see <<insert the name of the other document here>> for insn to set\n>>>   up an experimental smart HTTP server\" at the beginning of the original\n>>>   document.\n\nI meant to ask earlier but forgot.  Is this considered experimental still?\n\n> ... this one.\n>\n> I trust you can take care of the gitolite documentation side ;-)\n\n;-)\n"},{"id":"154231","messageId":"m3ocaljrs2.fsf@localhost.localdomain","threadId":"25513","inReplyTo":"AANLkTimTVviTBfY1Zeebyhufr36U+0w7VYf4f=25FMFi@mail.gmail.com","subject":"Re: should Documentation/howto/setup-git-server-over-http.txt be marked obsolete?","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2010-10-23T07:24:50Z","receivedAt":"2010-10-23T07:24:50Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Sitaram Chamarty <sitaramc@gmail.com> writes:\n> On Fri, Oct 22, 2010 at 8:36 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:\n>> Sitaram Chamarty wrote:\n>>\n>>> I assumed that the new -- much more efficient (correct?) transport\n>>> would make the older (dumber) transport obsolete, and I didn't realise\n>>> it had any advantages over the new one.\n>>\n>> FWIW the old transport still has its place.  If your web host (e.g.,\n>> an ISP) allows only static content (no CGI), then there is no choice.\n>>\n>> Not so relevant for gitolite but still relevant in the world.\n> \n> Also I now realise the new transport requires Apache, so people with\n> other web servers probably need it too.\n\nWhy do people think that \"smart\" HTTP transport requires Apache web\nserver?  If I understand it correctly provided git-http-backend is a\nsimple CGI script, and requires CGI-capable web server and git\ninstalled on server.  Examples use Apache because probably that is\nwhat author was familiar with.  I don't see the reason why it\nshouldn't work e.g. with nginx or IIS...\n\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"}]}