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

[Bradford C. Smith] [PATCH 2/2] use lockfile.c routines in git_commit_set_multivar()

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 25, 2007, 23:39 UTC
Message-ID
<7v7ioocatt.fsf@assigned-by-dhcp.cox.net>
    From: "Bradford C. Smith" <bradford.carl.smith@gmail.com>
    Subject: [PATCH 2/2] use lockfile.c routines in git_commit_set_multivar()
    Date: Wed, 25 Jul 2007 12:49:53 -0400
    Message-Id: <11853821962210-git-send-email-bradford.carl.smith@gmail.com>
    Changed git_commit_set_multivar() to use the routines provided by
    lockfile.c to reduce code duplication and ensure consistent behavior.
    Signed-off-by: "Bradford C. Smith" <bradford.carl.smith@gmail.com>

Dscho, I think this is worth doing regardless of that "symlinked config" issue. I haven't followed the code closely enough, though.

What do you think?
Next: Johannes Schindelin
Message 1 of 3 in “use lockfile.c routines in git_commit_set_multivar()”
  1. Junio C HamanoJul 25, 2007
  2. Johannes SchindelinJul 26, 2007
  3. Johannes SchindelinJul 26, 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.