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

Notes on http-push

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Nov 7, 2005, 18:34 UTC
Message-ID
<Pine.LNX.4.63.0511071926240.14149@wbgn013.biozentrum.uni-wuerzburg.de>
Hi,
two little things I noticed while playing around with http-push:
- if you init your test by git-clone'ing from a http repo, be sure to
	add a slash to the URL, else git-push will tell you erroneously
	that the server does not do DAV locking. (Probably http-push.c 
	should be fixed to add the slash when needed.)
- if you execute "git push origin", it does not do anything (correctly?),
	if there is no "Push:" line in .git/remotes/origin (which is the
	default after cloning). Try "git push origin master". (Probably
	http-push or git-push should say something about it, not
	just quit silently.)

If you want to play with it yourself: A minimal setup using Apache needs something like this in httpd.conf:

--- snip ---
<Location /gits>
  DAV on
  Deny From *
  Allow From 192.168.0.
</Location>

DAVLockDB "/usr/local/apache2/temp/DAV.lock" --- snap ---

Make sure that your www user has write permissions on <HTDOCS>/gits and on the DAV lock.

Have fun, Dscho

Next: Nick Hengeveld
Message 1 of 5 in “Notes on http-push”
  1. Johannes SchindelinNov 7, 2005
  2. Nick HengeveldNov 7, 2005
  3. Nick HengeveldNov 8, 2005
  4. Junio C HamanoNov 8, 2005
  5. Nick HengeveldNov 8, 2005

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.