git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: should Documentation/howto/setup-git-server-over-http.txt be marked obsolete?

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 22, 2010, 04:23 UTC
Message-ID
<7vsjzyrh2w.fsf@alter.siamese.dyndns.org>
In-Reply-To
<AANLkTimJe9vEUwWM482NLmfHGYjnsKD5RAryQO=Zyqjj@mail.gmail.com>
Sitaram Chamarty <sitaramc@gmail.com> 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.

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.
 - 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.
Previous: Sitaram ChamartyNext: Sitaram Chamarty
Message 2 of 8 in “should Documentation/howto/setup-git-server-over-http.txt be marked obsolete?”
  1. Sitaram ChamartyOct 22, 2010
  2. Junio C HamanoOct 22, 2010
  3. Sitaram ChamartyOct 22, 2010
  4. Jonathan NiederOct 22, 2010
  5. Sitaram ChamartyOct 23, 2010
  6. Jakub NarebskiOct 23, 2010
  7. Junio C HamanoOct 22, 2010
  8. Sitaram ChamartyOct 23, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.