From: Luke Diamand <luke@vidanti.com>
To: git@vger.kernel.org
Subject: Re: Problem with https and git-pull
Date: Thu, 08 Nov 2007 07:46:37 +0000 [thread overview]
Message-ID: <4732BEDD.3010703@vidanti.com> (raw)
In-Reply-To: <4732BDE6.4020509@vidanti.com>
OK, I just read the FAQ.
Luke Diamand wrote:
> I'm finding that git-pull using https does not work in the way I would
> expect.
>
> I created a bare repository, test.git, available by https://
>
> I then cloned it:
>
> % git-clone https://host/git/test.git
>
> So far, so good.
>
> Then I made a change in a different clone and pushed it.
>
> When I next did git-pull it just said:
>
> % git-pull
> Fetching refs/heads/master from https://host/git/test.git using https
> Already up-to-date.
>
> But it *isn't* up-to-date! If I do the same exercise with git:// or
> ssh:// on the same repo then it pulls down my changes as expected.
>
> Tried with:
> git version 1.5.3.4 (debian testing)
> git 1.5.3.5-dirty
>
> curl is 7.16.4
>
> The server access log shows the git-pull happening, and there are no
> errors reported by the server.
>
> Is there something obvious I'm missing?
>
> Thanks
> Luke
>
>
next prev parent reply other threads:[~2007-11-08 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 7:42 Problem with https and git-pull Luke Diamand
2007-11-08 7:46 ` Luke Diamand [this message]
2007-11-08 9:37 ` Andreas Ericsson
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=4732BEDD.3010703@vidanti.com \
--to=luke@vidanti.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).