From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Stephen & Linda Smith <ischis2@cox.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Missing Tagger Entry
Date: Thu, 30 Aug 2018 03:43:05 +0100 [thread overview]
Message-ID: <827dde10-9a7b-a7f1-76de-8ea079167d5e@ramsayjones.plus.com> (raw)
In-Reply-To: <2548439.nLQp1kU402@thunderbird>
On 30/08/18 02:56, Stephen & Linda Smith wrote:
> I am getting the following warning when runing a git fsck command against tag
> v0.99.
Yes, that is expected.
>
> $ git --version
> git version 2.18.0
>
> $ git fsck
> checking object directories: 100% (256/256), done.
> warning in tag d6602ec5194c87b0fc87103ca4d67251c76f233a: missingTaggerEntry:
> invalid format - expected 'tagger' line
> Checking objects: 100% (254339/254339), done.
> Checking connectivity: 254329, done.
This tag is so old that it dates to before a change in
the tag object format - in particular, before the 'tagger'
line was included. Viz:
$ git cat-file tag v0.99
object a3eb250f996bf5e12376ec88622c4ccaabf20ea8
type commit
tag v0.99
Test-release for wider distribution.
I'll make the first public RPM's etc, thus the tag.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQBC0b9oF3YsRnbiHLsRAlUUAKCJEyvw8tewGFKd/A3aCd82Wi/zAgCgl7z4
GYPjO+Xio0IvuEYsrhFc2KI=
=TVVN
-----END PGP SIGNATURE-----
$
Note the lack of a 'tagger' line, unlike a more up-to-date tag:
$ git cat-file tag v2.18.0
object 53f9a3e157dbbc901a02ac2c73346d375e24978c
type commit
tag v2.18.0
tagger Junio C Hamano <gitster@pobox.com> 1529600438 -0700
Git 2.18
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEE4fA2sf7nIh/HeOzvsLXohpav5ssFAlsr2bYACgkQsLXohpav
5suqEhAAgDu2A1n9G7ik+HdKoH2VNGwDqaRu/3k8znLPR6NmcOpHqopCgaxPYN4T
gH69ff+8Le8NiOYcoWaOE2WdpGGY9Gu12N65MpxYbEhehEGo7ze4T8jDNlHz7q5B
XC55FKHAwqy51NtdzvqNgsptc3bASy+ThxNM5XS0GSeqz00ublquHhiGTzhkBKm2
KbexWhGWjzq0zP+wOrRIX4zU1lAOHXzjVV7G8vo3pTcg+GgK0BmiAz8zmOlef2au
SYlU2LJCcQFm12j7pdDx42qCfZYM3QB0vJkHAcEdKYlcSEKRYUdOEnIQHxHwPPvB
A/uogytfeExnpBd/aHA/YBKlr8FNBMZeDKGHiwxWsBK5yExxfelIFnOg27YBIxl2
zzbMnHubBqHs5luo2Yv9JmFCbmuqV6ei6qgDKn2BXtJkuXVqYI1FYuKQyO26b3cz
C6hF5n3OIixL0wv1S+44QqDEc/ss8kvqosT2Ypjd56dNeZripTe3jC+bqUouHblD
NGaUn+V2YGBKc3rPw1UE3WnXgqOcbyvxn8AoZIKhJveaq7z89CbcvQYpqNjGhmrp
OvqSVG3NUoOKGXiMAg4/a4wx6JWTyu5SLHY269tC3cPfxQkD3br6hMsBy+AXrCwq
5yk6A3kQ2d6S9QfbWr6PGT7FI/AhG9CftFXPjpF0h9W9xbPJfkE=
=ResM
-----END PGP SIGNATURE-----
$
You can suppress this warning by using an fsck 'skiplist':
1) Add the following lines to your .git/config file:
[fsck]
skiplist = .git/skip
2) Add the object-id of the v0.99 tag to the skiplist file:
$ echo d6602ec5194c87b0fc87103ca4d67251c76f233a >.git/skip
Hope this helps.
ATB,
Ramsay Jones
next prev parent reply other threads:[~2018-08-30 2:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 1:56 Missing Tagger Entry Stephen & Linda Smith
2018-08-30 2:43 ` Ramsay Jones [this message]
2018-08-30 3:18 ` Stephen & Linda Smith
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=827dde10-9a7b-a7f1-76de-8ea079167d5e@ramsayjones.plus.com \
--to=ramsay@ramsayjones.plus.com \
--cc=git@vger.kernel.org \
--cc=ischis2@cox.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).