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
Junio C Hamano <gitster@pobox.com>
Date
Sep 28, 2011, 18:50 UTC
Message-ID
<7vsjngzelc.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1317225869.30267.18.camel@bee.lab.cmartin.tk>
Carlos Martín Nieto <cmn@elego.de> writes:
> Whilst trying to do some work related to fetch, I came across a
> regression in the 'next' branch....
>
> $ ./git-fetch git://repo.or.cz/git
That invocation of ./git-fetch looks suspicious.

Are you sure that it internally invokes ./git-rev-list from the same version that knows --verify-objects option (you just built in your current directory), or is it invoking an old git-rev-list that is installed and is reachable from your usual $PATH, which does not know that option yet?

When I try a new version that was just built in my current directory, here is an incantation I use:

    GIT_EXEC_PATH=`pwd`
    PATH=`pwd`:/usr/bin:/bin
    GITPERLLIB=`pwd`/perl/blib/lib
    export GIT_EXEC_PATH PATH GITPERLLIB
Previous: Carlos Martín NietoNext: Jeff King
Message 2 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.