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

Re: [PATCH] introduce inline is_same_sha1

From
Alex Riesen <raa.lkml@gmail.com>
Date
Aug 17, 2006, 11:59 UTC
Message-ID
<81b0412b0608170459if099fcane9d9e91a3fdac9e6@mail.gmail.com>
In-Reply-To
<Pine.LNX.4.63.0608161721020.11465@chino.corp.google.com>
On 8/17/06, David Rientjes <rientjes@google.com> wrote:
> Introduces global inline:
>         is_same_sha1(const unsigned char *sha1,
>                      const unsigned char *sha2);

It is longer and negates all (like in "lots") previous callsites of memcmp. Are sure you didn't do a trivial typo somewhere?

Why not just sha1cmp? And if you're aiming at hash-type independence, why not hashcmp?

Previous: Junio C HamanoNext: David Rientjes
Message 5 of 8 in “introduce inline is_same_sha1”
  1. introduce inline is_same_sha1David Rientjes, Aug 17, 2006
  2. Junio C HamanoAug 17, 2006
  3. David RientjesAug 17, 2006
  4. Junio C HamanoAug 17, 2006
  5. Alex RiesenAug 17, 2006
  6. David RientjesAug 17, 2006
  7. Alex RiesenAug 17, 2006
  8. Junio C HamanoAug 18, 2006

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.