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

Re: Is git over http (git-http-push) ready for production ?

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Feb 19, 2010, 13:46 UTC
Message-ID
<vpqr5ohz6bk.fsf@bauges.imag.fr>
In-Reply-To
<hllp07$o78$1@ger.gmane.org>
Fabien <fabien.ubuntu@gmail.com> writes:
Show 5 quoted lines
> Hi,
>
> Following my last email about locks problem with reiserfs (see
> git-http-push (git v1.5) problems with DAVLockDB on reiserfs FS), I was
> wondering how reliable is git-http-push.

My experience is: it mostly works, but sometimes break, usually doesn't give very helpfull messages when you mis-use it, ...

Rather clearly, git-http-push doesn't have as many users as ssh://, read-only http:// and git://, and therefore doesn't have as many testers/developers.

If "production" means "many users" and "need for something unbreakable", then perhaps the HTTP smart protocol is more promising.

But that's just my experience.
-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Tay Ray ChuanNext: Ilari Liusvaara
Message 3 of 6 in “Is git over http (git-http-push) ready for production ?”
  1. FabienFeb 19, 2010
  2. Tay Ray ChuanFeb 19, 2010
  3. Matthieu MoyFeb 19, 2010
  4. Ilari LiusvaaraFeb 19, 2010
  5. FabienFeb 19, 2010
  6. Shawn PearceFeb 19, 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.