From: Jeff King <peff@peff.net>
To: Daniel Devlin <devlin-d1@email.ulster.ac.uk>
Cc: git@vger.kernel.org
Subject: Re: could not verify object error
Date: Fri, 13 Feb 2015 04:56:31 -0500 [thread overview]
Message-ID: <20150213095630.GA32009@peff.net> (raw)
In-Reply-To: <loom.20150212T132927-657@post.gmane.org>
On Thu, Feb 12, 2015 at 12:32:45PM +0000, Daniel Devlin wrote:
> tag_contents =
> "object f849f9e28c7f36a826d4b451efb16516c0c3acc2\ntype #{type}\ntag #
> {tagname}\ntagger #{username} <#{email}> #{Time.new.to_i} +0000\n\n#{message}"
> [...]
> executecommand = "printf \"#{tag_contents}\" | git mktag"
> [...]
> I have tried to run it on a vm with git 2.0.4 but keep
> getting char 7 could not verify object error message.
Do you have object f849f9e28c... in the repository where you are running
mktag? If so, is it a commit object, as you are putting in the type
field? What does:
git cat-file -t f849f9e28c7f36a826d4b451efb16516c0c3acc2
show?
-Peff
prev parent reply other threads:[~2015-02-13 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 12:32 could not verify object error Daniel Devlin
2015-02-13 9:56 ` Jeff King [this message]
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=20150213095630.GA32009@peff.net \
--to=peff@peff.net \
--cc=devlin-d1@email.ulster.ac.uk \
--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).