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

Re: warning: no common commits - slow pull

From
DBDavid Brownell <david-b@pacbell.net>
Date
Mar 8, 2008, 23:25 UTC
Message-ID
<200803081525.08181.david-b@pacbell.net>
In-Reply-To
<alpine.LNX.1.00.0803081750580.19665@iabervon.org>
On Saturday 08 March 2008, Daniel Barkalow wrote:
Show 7 quoted lines
> On Sat, 8 Mar 2008, David Brownell wrote:
> > Oddly, a few times when I tried that the bug didn't reproduce.
> > One factor may be workspaces cloned a long time ago with early
> > versions of GIT (or cogito).
> 
> Is it a few times on different workspaces, or with copies of the same 
> workspace?

I had several workspaces that weren't updated ... which by previous experience should *all* have done an extra update. I did the pull with the GIT_DEBUG on a few of them, and the bogus one didn't happen.

This seemed odd to me so the next time I tried without the GIT_DEBUG thing ... and got the bogus pull with "no common commits". This was unfortunately *after* I deleted tarballs of the previous workspaces, so that exact experiment can't be reproduced. Those were, however, "newer" workspaces -- probably created last summer, rather than a few years ago.

> I think that there's a dependance on how your current state and  
> the new state happen to line up.

The workspace in the tarball I can send you doesn't have any issues with reproducibility ... now. 

- Dave
Previous: Daniel BarkalowNext: Daniel Barkalow
Message 5 of 9 in “Re: warning: no common commits - slow pull”
  1. David BrownellMar 7, 2008
  2. Daniel BarkalowMar 8, 2008
  3. David BrownellMar 8, 2008
  4. Daniel BarkalowMar 8, 2008
  5. David BrownellMar 8, 2008
  6. Daniel BarkalowMar 8, 2008
  7. Daniel BarkalowMar 9, 2008
  8. David BrownellMar 10, 2008
  9. Daniel BarkalowMar 10, 2008

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.