From: "James Youngman" <jay@gnu.org>
To: git@vger.kernel.org
Subject: Clarifying "invalid tag signature file" error message from git filter-branch (and others)
Date: Thu, 11 Dec 2008 10:14:03 +0000 [thread overview]
Message-ID: <c5df85930812110214k2e12d926m60856fb630d45e80@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
What do the errors "error: char88: malformed tagger field" and "fatal:
invalid tag signature file" and "Could not create new tag object for
FINDUTILS-4_1-10" signify in the session below?
Are any of those errors correctable (I can re-run the tree rewrite
script as many times as needed, I'm just using it on a test repository
for now).
The script I'm invoking calls git filter-branch; I've attached the script.
$ bash ~/source/GNU/findutils/logrewrite.sh
fatal: Not a git repository
Rewrite 9afb13614381c4bfa22f515c18cbfe6f54798330 (1587/1587)
Ref 'refs/heads/master' was rewritten
FINDUTILS-4_1-10 -> FINDUTILS-4_1-10
(ce25eb352de8dc53a9a7805ba9efc1c9215d28c2 ->
79221244237bc408ced0c37f3c3476d53e665801)
error: char88: malformed tagger field
fatal: invalid tag signature file
Could not create new tag object for FINDUTILS-4_1-10
$
Thanks,
James.
[-- Attachment #2: logrewrite.sh --]
[-- Type: application/x-sh, Size: 1401 bytes --]
next reply other threads:[~2008-12-11 10:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 10:14 James Youngman [this message]
2008-12-11 21:06 ` Clarifying "invalid tag signature file" error message from git filter-branch (and others) Brandon Casey
2008-12-11 22:34 ` James Youngman
2008-12-11 23:13 ` Brandon Casey
2008-12-11 23:59 ` James Youngman
2008-12-12 11:02 ` Jim Meyering
2008-12-12 16:05 ` James Youngman
2008-12-12 16:44 ` Brandon Casey
2008-12-12 16:53 ` Jakub Narebski
2008-12-12 16:21 ` Brandon Casey
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=c5df85930812110214k2e12d926m60856fb630d45e80@mail.gmail.com \
--to=jay@gnu.org \
--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).