From: "James Youngman" <jay@gnu.org>
To: "Brandon Casey" <casey@nrlssc.navy.mil>
Cc: git@vger.kernel.org, "Jim Meyering" <jim@meyering.net>
Subject: Re: Clarifying "invalid tag signature file" error message from git filter-branch (and others)
Date: Thu, 11 Dec 2008 23:59:29 +0000 [thread overview]
Message-ID: <c5df85930812111559p287ea6afk54a9759302288d5e@mail.gmail.com> (raw)
In-Reply-To: <LhfS_uc2B_Gje7rXd1882RMsQfSRjOEsBT24Z1Yza_bWhgl9lI-ZhQ@cipher.nrlssc.navy.mil>
On Thu, Dec 11, 2008 at 11:13 PM, Brandon Casey <casey@nrlssc.navy.mil> wrote:
>> Before conversion:
>> $ git cat-file tag FINDUTILS-4_1-10
>> object ce25eb352de8dc53a9a7805ba9efc1c9215d28c2
>> type commit
>> tag FINDUTILS-4_1-10
>> tagger Kevin Dalley
>
> The tagger field is missing an email address, a timestamp, and a timezone. It
> should look something like:
>
> tagger Kevin Dalley <kevin.dalley@somewhere.com> 1229036026 -0800
>
> git-mktag prevents improperly formatted tags from being created by checking
> that these fields exist and are well formed.
>
> If you know the correct values for the missing fields, then you could
Yes for the email address. But as for the timestamp, it's not in
the tag file; that only contains the sha1.
There is a timestamp in the object being tagged, is that the timestamp
you are talking about?
$ git show --pretty=raw ce25eb352de8dc53a9a7805ba9efc1c9215d28c2
commit ce25eb352de8dc53a9a7805ba9efc1c9215d28c2
tree 752cca144d39bc55d05fbe304752b274ba22641c
parent 9a998755249b0c8c47e8657cff712fa506aa30fc
author Kevin Dalley <kevin@seti.org> 830638152 +0000
committer Kevin Dalley <kevin@seti.org> 830638152 +0000
*** empty log message ***
diff --git a/debian.Changelog b/debian.Changelog
index e3541eb..d0cd295 100644
--- a/debian.Changelog
+++ b/debian.Changelog
@@ -1,5 +1,7 @@
Sat Apr 27 12:29:06 1996 Kevin Dalley
<kevin@aplysia.iway.aimnet.com (Kevin Dalley)>
+ * find.info, find.info-1, find.info-2: updated to match find.texi
+
* debian.rules (debian): update debian revision to 10
* getline.c (getstr): verify that nchars_avail is *really* greater
> recreate the tags before doing the filter-branch. If they are unknown, it
> seems valid enough to use the values from the commit that the tag points
> to.
>
> i.e.
>
> tagger Kevin Dalley <kevin@seti.org> 830638152 -0000
>
> What tool was used to convert this repository to git? It should be corrected
> to produce valid annotated tags. Especially if it is a tool within git.
I don't know, Jim Meyering will know though, so I CC'ed him.
> The tag below was actually not converted. filter-branch bailed
> out during the conversion and so left it alone.
I see.
Thanks,
James.
next prev parent reply other threads:[~2008-12-12 0:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 10:14 Clarifying "invalid tag signature file" error message from git filter-branch (and others) James Youngman
2008-12-11 21:06 ` Brandon Casey
2008-12-11 22:34 ` James Youngman
2008-12-11 23:13 ` Brandon Casey
2008-12-11 23:59 ` James Youngman [this message]
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=c5df85930812111559p287ea6afk54a9759302288d5e@mail.gmail.com \
--to=jay@gnu.org \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=jim@meyering.net \
/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).