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

Re: Problem with https and git-pull

From
LDLuke Diamand <luke@vidanti.com>
Date
Nov 8, 2007, 07:46 UTC
Message-ID
<4732BEDD.3010703@vidanti.com>
In-Reply-To
<4732BDE6.4020509@vidanti.com>
OK, I just read the FAQ.
Luke Diamand wrote:
Show 37 quoted lines
> 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
> 
> 
Previous: Luke DiamandNext: Andreas Ericsson
Message 2 of 3 in “Problem with https and git-pull”
  1. Luke DiamandNov 8, 2007
  2. Luke DiamandNov 8, 2007
  3. Andreas EricssonNov 8, 2007

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.