Re: [StGit PATCH] Parse commit object header correctly

From: Catalin Marinas <catalin.marinas@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Karl Hasselström" <kha@treskal.com>,
	"Andy Green (林安廸)" <andy@warmcat.com>,
	git@vger.kernel.org
Subject: Re: [StGit PATCH] Parse commit object header correctly
Date: Thu, 9 Feb 2012 09:38:00 +0000	[thread overview]
Message-ID: <CAHkRjk6dr=5wxm+iSC2_CSB-q3k2WG_Um+X7dwsy-H8tL508EA@mail.gmail.com> (raw)
In-Reply-To: <7vd39pzsmq.fsf_-_@alter.siamese.dyndns.org>

Hi Junio,

On 8 February 2012 07:33, Junio C Hamano <gitster@pobox.com> wrote:
> To allow parsing the header produced by versions of Git newer than the
> code written to parse it, all commit parsers are expected to skip unknown
> header lines, so that newer types of header lines can be added safely.
> The only three things that are promised are:
>
>  (1) the header ends with an empty line (just an LF, not "a blank line"),
>  (2) unknown lines can be skipped, and
>  (3) a header "field" begins with the field name, followed by a single SP
>     followed by the value.

Thanks for looking into this. Is this the same as an email header? If
yes, we could just use the python's email.Header.decode_header()
function (I haven't tried yet).

BTW, does Git allow custom headers to be inserted by tools like StGit?

-- 
Catalin