From: Junio C Hamano <gitster@pobox.com>
To: Wolfgang Denk <wd@denx.de>
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: git error in tag ...: unterminated header
Date: Thu, 25 Jun 2015 13:24:49 -0700 [thread overview]
Message-ID: <xmqqegkzy1ri.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20150625201309.5026A384E81@gemini.denx.de> (Wolfgang Denk's message of "Thu, 25 Jun 2015 22:13:09 +0200")
Wolfgang Denk <wd@denx.de> writes:
> Dear Junio,
>
> thanks for the fast replies.
>
> In message <xmqqegkzzoaz.fsf@gitster.dls.corp.google.com> you wrote:
>>
>> > Question is: how can we fix that?
>>
>> It could be that 4d0d8975 is buggy and barking at a non breakage.
>>
>> If there is no message in the tag, i.e.
>>
>> -- 8< --
>> object 84ef51a632063e8cb57b2e9a4252497512831ffe
>> type commit
>> tag LABEL_2006_03_12_0025
>> tagger Wolfgang Denk <wd@pollux.denx.de> 1142119613 +0100
>> -- >8 --
>
> It seems recent tools cannot create such tags any more?
Yeah, we append an extra blank line after the last header even when
there is no message. But I do not think that means what you have
above is invalid.
next prev parent reply other threads:[~2015-06-25 20:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 15:51 git error in tag ...: unterminated header Wolfgang Denk
2015-06-25 17:32 ` Junio C Hamano
2015-06-25 20:13 ` Wolfgang Denk
2015-06-25 20:24 ` Junio C Hamano [this message]
2015-06-25 21:07 ` Johannes Schindelin
2015-06-25 21:21 ` Junio C Hamano
2015-06-25 22:29 ` Junio C Hamano
2015-06-26 8:06 ` Johannes Schindelin
2015-06-26 15:52 ` Jeff King
2015-06-26 17:37 ` Junio C Hamano
2015-06-27 8:57 ` Johannes Schindelin
2015-06-27 18:36 ` Junio C Hamano
2015-06-28 18:18 ` [PATCH] fsck: it is OK for a tag and a commit to lack the body Junio C Hamano
2015-06-28 18:21 ` Eric Sunshine
2015-06-29 5:12 ` Johannes Schindelin
2015-06-29 5:42 ` Junio C Hamano
2015-06-29 14:51 ` Johannes Schindelin
2015-06-25 20:48 ` git error in tag ...: unterminated header Junio C Hamano
2015-06-25 17:38 ` Junio C Hamano
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=xmqqegkzy1ri.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=wd@denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.