From: Tay Ray Chuan <rctay89@gmail.com>
To: Fabien <fabien.ubuntu@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Is git over http (git-http-push) ready for production ?
Date: Fri, 19 Feb 2010 19:14:41 +0800 [thread overview]
Message-ID: <be6fef0d1002190314n4300aed3uc58d812b83342db2@mail.gmail.com> (raw)
In-Reply-To: <hllp07$o78$1@ger.gmane.org>
Hi,
On Fri, Feb 19, 2010 at 6:26 PM, Fabien <fabien.ubuntu@gmail.com> wrote:
> I had to delete the davlock file and restart apache to solve the issue.
I guess this is a regression. Before remote helpers were introduced,
the dumb http-push program was able to release locks on the remote
side on such signals.
> So, this operation doesn't seem really atomic ?
Overall, git-push over dav isn't atomic. At most, it is atomic at the
individual object level - for example, you won't get a blob with SHA-1
"abc123" but hashes to a different SHA-1 value.
> Another problem I see is the password in clear text in ~/.netrc to avoid
> to type passwords all the time.
Might sound pathetic, but you could chmod it to make it readable only
to yourself.
> 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.
You said it yourself. :)
If you really think .netrc isn't your cup of tea, you could tunnel through ssh.
--
Cheers,
Ray Chuan
next prev parent reply other threads:[~2010-02-19 11:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 10:26 Is git over http (git-http-push) ready for production ? Fabien
2010-02-19 11:14 ` Tay Ray Chuan [this message]
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=be6fef0d1002190314n4300aed3uc58d812b83342db2@mail.gmail.com \
--to=rctay89@gmail.com \
--cc=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).