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

Suggestion: improve cherry-pick message in case object is not found

From
Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
Date
Aug 9, 2011, 09:58 UTC
Message-ID
<CAA01CsosJJb1suq2YDmcFKPdBD4yHWXrENfCP0mewDEhsFjcOg@mail.gmail.com>
Hi,

I'd like to suggest improving message displayed by cherry-pick (and others?) when it's given non-existing sha1. For example:

$ git cherry-pick 2ac2d6d5997de01b84de54fe8ac5c7d6bba139ca fatal: bad object 2ac2d6d5997de01b84de54fe8ac5c7d6bba139ca

The "fatal: bad object" suggest to me that the object is found but is incorrect/corrupted. It took me some time (in which I managed to run git fsck) to find out that I ran this git on wrong repository, which did not have object with this sha1.

Is it possible to change this message to for example: fatal: could not find object 2ac2d6d5997de01b84de54fe8ac5c7d6bba139ca

Thanks,
-- 
Piotr Krukowiecki
Message 1 of 1 in “Suggestion: improve cherry-pick message in case object is not found”
  1. Piotr KrukowieckiAug 9, 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.