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

Re: [PATCH 1/2] Sanitize for_each_reflog_ent()

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 9, 2007, 09:57 UTC
Message-ID
<Pine.LNX.4.63.0701091056520.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<enumq8$oa$1@sea.gmane.org>
Hi,
On Tue, 9 Jan 2007, Jakub Narebski wrote:
Show 20 quoted lines
> Johannes Schindelin wrote:
> 
> > On Sun, 7 Jan 2007, Junio C Hamano wrote:
> > 
> >> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> >> 
> >>> Further, it makes no sense to force the parsing upon the helper
> >>> functions; for_each_reflog_ent() now calls the helper function with
> >>> old and new sha1, the email, the timestamp & timezone, and the message.
> >> 
> >> Perhaps.  I did it that way deliberately because all existing
> >> users did not have to pay overhead of parsing.
> > 
> > My reasoning is that invalid entries should rather be ignored than be 
> > taken into account. So, to verify that you are not walking invalid data, 
> > you have to parse it anyway.
> 
> I think that Junio was talking about the fact, that if you for example
> do need only refname and sha1, there is no need to parse object at all.
> If you don't need to, don't parse.
And it was exactly what _I_ was talking about, too:

if there are invalid entries, you ignore them. So for example, if there is no timestamp and message, you don't want the osha1 or nsha1, because it is an _invalid_ record.

Ciao, Dscho

Previous: Jakub NarebskiNext: Junio C Hamano
Message 5 of 7 in “Sanitize for_each_reflog_ent()”
  1. 1/2 Sanitize for_each_reflog_ent()Johannes Schindelin, Jan 8, 2007
  2. Junio C HamanoJan 8, 2007
  3. Johannes SchindelinJan 8, 2007
  4. Jakub NarebskiJan 9, 2007
  5. Johannes SchindelinJan 9, 2007
  6. Junio C HamanoJan 9, 2007
  7. Johannes SchindelinJan 9, 2007

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.