git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] git-fsck: report missing author/commit line in a commit as an error

From
MKMartin Koegler <mkoegler@auto.tuwien.ac.at>
Date
Jan 21, 2008, 07:00 UTC
Message-ID
<20080121070049.GA18819@auto.tuwien.ac.at>
In-Reply-To
<alpine.LSU.1.00.0801201918260.5731@racer.site>
On Sun, Jan 20, 2008 at 07:20:54PM +0000, Johannes Schindelin wrote:
Show 8 quoted lines
> Hi,
> 
> On Sun, 20 Jan 2008, Martin Koegler wrote:
> 
> > +	if (!commit->date)
> > +		return objerror(&commit->object, "invalid author/commiter line in %s",
> 
> s/commiter/committer/
Thanks. Will change in next version.
Show 5 quoted lines
> It makes me wonder, though, if that's correct.  AFAICT it is the committer 
> date, and the rest of the line _might_ be just fine.
>
> Why not be less intrusive and just change the printf() into a return 
> objerror(), like the commit message suggests?
parse_commit_date returns zero, if
* the author line is missing
* the author line is not terminated with \n
* the committer line is missing
* the committer line does not contain >
* the > is not followed by a number bigger than zero
* the commiter line is not terminated with \n
So, in my option the message "bad commit date in %s" is incorrect/misleading.
fsck_commit could be further simplified:
//  If tree is missing, parse_commit should return zero => fsck_commit would not be called 
-        if (memcmp(buffer, "tree ", 5))
-                return objerror(&commit->object, "invalid format - expected 'tree' line");
//  If sha1 is missing/incorrect, parse_commit should return zero => fsck_commit would not be called 
-        if (get_sha1_hex(buffer+5, tree_sha1) || buffer[45] != '\n')
-                return objerror(&commit->object, "invalid 'tree' line format - bad sha1");
         buffer += 46;
         while (!memcmp(buffer, "parent ", 7)) {
//  If sha1 is missing/incorrect, parse_commit should return zero => fsck_commit would not be called 
-                if (get_sha1_hex(buffer+7, sha1) || buffer[47] != '\n')
-                        return objerror(&commit->object, "invalid 'parent' line format - bad sha1");
                buffer += 48;
         }
         if (memcmp(buffer, "author ", 7))
                 return objerror(&commit->object, "invalid format - expected 'author' line");
I'm not sure, if this 6 lines should be dropped too.

The memcmp(buffer, "author ", 7) check is already done by (!commit->date), but I prefer to keep it, as further committer/author line checks can be based on it.

mfg Martin Kögler PS: While writting this mail, I noticed that parse_object_buffer does not check the return value of parse_XX_buffer. I'll send a patch, which correct this.

Previous: Johannes Schindelin
Message 3 of 3 in “git-fsck: report missing author/commit line in a commit as an error”
  1. git-fsck: report missing author/commit line in a commit as an errorMartin Koegler, Jan 20, 2008
  2. Johannes SchindelinJan 20, 2008
  3. Martin KoeglerJan 21, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.