git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabien <fabien.ubuntu@gmail.com>
To: git@vger.kernel.org
Subject: Is git over http (git-http-push) ready for production ?
Date: Fri, 19 Feb 2010 11:26:16 +0100	[thread overview]
Message-ID: <hllp07$o78$1@ger.gmane.org> (raw)

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.

I was able to reproduce the same problem, also with client 1.6.6.2, when
interrupting the command in the middle.

$ git push origin master
Fetching remote heads...
  refs/
  refs/tags/
  refs/heads/
updating 'refs/heads/master'
  from a0f6d85d90a52a28628f29765eb61de559c1fd31
  to   952622ca0f55e76d810a5dc7a1dd1c8c44f8a7d7
Removing remote locks...

=> interrupted by Ctrl+C

$ git push origin master
Fetching remote heads...
  refs/
  refs/tags/
  refs/heads/
updating 'refs/heads/master'
  from a0f6d85d90a52a28628f29765eb61de559c1fd31
  to   952622ca0f55e76d810a5dc7a1dd1c8c44f8a7d7
Unable to lock remote branch refs/heads/master
Updating remote server info
fatal: git-http-push failed


I had to delete the davlock file and restart apache to solve the issue.
So, this operation doesn't seem really atomic ?

Another problem I see is the password in clear text in ~/.netrc to avoid
  to type passwords all the time.
Is there any plan to address this problem ? There used to be the same
case in subversion (yep, sorry for the comparison), and they finally
addressed that by supporting GNOME Keyring and KWallet.
For what I saw, http support is provided thru libcurl, so it may not be
that easy.

Finally, hooks don't work when using git over http (yep, I know, it's a
"dumb" protocol)...

Sorry for blaming you and thanks a lot for your help :)

--
Fabien

             reply	other threads:[~2010-02-19 10:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19 10:26 Fabien [this message]
2010-02-19 11:14 ` Is git over http (git-http-push) ready for production ? Tay Ray Chuan
2010-02-19 13:46 ` Matthieu Moy
2010-02-19 14:04 ` Ilari Liusvaara
2010-02-19 15:08   ` Fabien
2010-02-19 19:05     ` Shawn Pearce

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='hllp07$o78$1@ger.gmane.org' \
    --to=fabien.ubuntu@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).