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

Re: 6d4bb3833c3d2114d (fetch: verify we have everything we need before updating our ref) breaks fetch

From
Jakub Narebski <jnareb@gmail.com>
Date
Sep 28, 2011, 19:12 UTC
Message-ID
<m3y5x8o527.fsf@localhost.localdomain>
In-Reply-To
<1317225869.30267.18.camel@bee.lab.cmartin.tk>
Carlos Martín Nieto <cmn@elego.de> writes:
Show 11 quoted lines
> Hello,
> 
> Whilst trying to do some work related to fetch, I came across a
> regression in the 'next' branch. Bisecting gave me this commit as
> breaking point (and I tried with the parent and there it worked). When
> doing 'git fetch', rev-list will complain about usage, and fetch will
> say that we didn't receive enough, even though earlier versions of git
> have no problems. This fails both on github and on git.or.cz and for git
> and http transports:
> 
> $ ./git-fetch git://repo.or.cz/git
Have you tried
  $ ./git fetch git://repo.or.cz/git
?
-- 
Jakub Narębski
Previous: Carlos Martín NietoNext: Carlos Martín Nieto
Message 5 of 9 in “6d4bb3833c3d2114d (fetch: verify we have everything we need before updating our ref) breaks fetch”
  1. Carlos Martín NietoSep 28, 2011
  2. Junio C HamanoSep 28, 2011
  3. Jeff KingSep 28, 2011
  4. Carlos Martín NietoSep 30, 2011
  5. Jakub NarebskiSep 28, 2011
  6. Carlos Martín NietoSep 30, 2011
  7. Jeff KingOct 1, 2011
  8. Philip OakleyOct 1, 2011
  9. Jeff KingOct 1, 2011

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.