From: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Suggestion: improve cherry-pick message in case object is not found
Date: Tue, 9 Aug 2011 11:58:01 +0200 [thread overview]
Message-ID: <CAA01CsosJJb1suq2YDmcFKPdBD4yHWXrENfCP0mewDEhsFjcOg@mail.gmail.com> (raw)
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
reply other threads:[~2011-08-09 9:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA01CsosJJb1suq2YDmcFKPdBD4yHWXrENfCP0mewDEhsFjcOg@mail.gmail.com \
--to=piotr.krukowiecki@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).