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

Re: [PATCH 1/2] fsck_commit_buffer(): do not special case the last validation

From
Jeff King <peff@peff.net>
Date
Apr 14, 2016, 18:10 UTC
Message-ID
<20160414181030.GA22068@sigill.intra.peff.net>
In-Reply-To
<20160414180709.28968-1-gitster@pobox.com>
On Thu, Apr 14, 2016 at 11:07:08AM -0700, Junio C Hamano wrote:
Show 28 quoted lines
> The pattern taken by all the validations in this function is:
> 
> 	if (notice a violation exists) {
> 		err = report(... VIOLATION_KIND ...);
> 		if (err)
> 			return err;
> 	}
> 
> where report() returns zero if specified kind of violation is set to
> be ignored, and otherwise shows an error message and returns non-zero.
> 
> The last validation in the function immediately after the function
> returns 0 to declare "all good" can cheat and directly return the
> return value from report(), and the current code does so, i.e.
> 
> 	if (notice a violation exists)
> 		return report(... VIOLATION_KIND ...);
> 	return 0;
> 
> But that is a selfish code that declares it is the ultimate and
> final form of the function, never to be enhanced later.  To allow
> and invite future enhancements, make the last test follow the same
> pattern.
> 
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
>  fsck.c | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
Patch looks good, and nicely explained.
-Peff
Previous: Johannes SchindelinNext: Junio C Hamano
Message 10 of 13 in “fsck_commit_buffer(): do not special case the last validation”
  1. 1/2 fsck_commit_buffer(): do not special case the last validationJunio C Hamano, Apr 14, 2016
  2. 2/2 fsck: detect and warn a commit with embedded NULJunio C Hamano, Apr 14, 2016
  3. Jeff KingApr 14, 2016
  4. Junio C HamanoApr 14, 2016
  5. Jeff KingApr 14, 2016
  6. Junio C HamanoApr 14, 2016
  7. Jeff KingApr 14, 2016
  8. Junio C HamanoApr 14, 2016
  9. Johannes SchindelinApr 15, 2016
  10. Jeff KingApr 14, 2016
  11. Junio C HamanoApr 14, 2016
  12. Johannes SchindelinApr 15, 2016
  13. Junio C HamanoApr 15, 2016

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.