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

Trouble building newer git with older

From
NANishanth Aravamudan <nacc@us.ibm.com>
Date
Aug 8, 2006, 18:47 UTC
Message-ID
<20060808184716.GC4546@us.ibm.com>
Hi all,

I am in the process of updating one of our system's set of git binaries and noticed the following. When executing

git clone rsync://rsync.kernel.org/pub/scm/git/git.git git cd git git checkout make

I get this error:
kernel:/home/nacc/download/git# make
GIT_VERSION = Usage: git COMMAND [OPTIONS] [TARGET]
 git command 'describe' not found: commands are:
    add apply archimport bisect branch checkout cherry clone
    commit count.objects cvsimport diff fetch format.patch
    fsck.cache get.tar.commit.id init.db log ls.remote octopus
    pack.objects parse.remote patch.id prune pull push rebase
    relink rename repack request.pull reset resolve revert
    send.email shortlog show.branch status tag verify.tag
    whatchanged-dirty
GIT-VERSION-FILE:2: *** multiple target patterns.  Stop.

This is because GIT-VERSION-GEN attempts to invoke `git describe` but describe is not a valid parameter to the current version of git. This is not treated as a failure case, though, as output is stored in VN. Perhaps the return code of `git describe` should also be checked? Or am I just not supposed to upgrade from this old of a version of git via git?

Thanks, Nish

-- 
Nishanth Aravamudan <nacc@us.ibm.com>
IBM Linux Technology Center
Next: Junio C Hamano
Message 1 of 3 in “Trouble building newer git with older”
  1. Nishanth AravamudanAug 8, 2006
  2. Junio C HamanoAug 8, 2006
  3. Nishanth AravamudanAug 8, 2006

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.