Re: Gnus Git repository info and comitters: need updated password

[Katsumi Yamaoka <yamaoka@jpl.org>]

>>>>> Ted Zlatanov wrote:
> On Thu, 15 Apr 2010 15:50:59 +0900 Katsumi Yamaoka <yamaoka@jpl.org> wrote:
[...]
KY> Did anyone succeed in cloning the writable repo behind the firewall
KY> (or http proxy)?  If so, how?  I haven't made good yet.  Using
KY> 80.91.231.55 instead of the host name made no difference, either.
[...]
> Behind a firewall, you can probably use the curl options (in ~/.curlrc)
> to control the behavior.  See GIT_CURL_VERBOSE and try to replicate what
> it does when it fails.

I did it!  The Gnus Git repo and the Emacs trunk is now synch'd
(the recent changes made in gnus.texi in the emacs-23 branch
will be merged to the trunk later).

First, I found I need setting of the environment variable
`HTTPS_PROXY' rather than `http_proxy':

export HTTPS_PROXY=proxy.example.com:8080

Second, I didn't know git-remote-https (or git-remote-curl) reads
the ~/.netrc file, but it cannot handle password containing SPC.
I use just such a password "PASS WORD", and I found out the only
way to pass it to Git is:

git clone 'https://yamaoka:PASS WORD@git.gnus.org/gnus.git'

But that the ps command exposes it is bad from every point of view.
I'll ask Ted to change it into the one that doesn't contain SPC.

Regards,