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

[PATCH 0/1] incremental update against 'next' branch

From
Kyle J. McKay <mackyle@gmail.com>
Date
Jul 19, 2013, 00:16 UTC
Message-ID
<3e0c11386c2e091f09c554bf0ba091d@f74d39fa044aa309eaea14b9f57fe79>
NOTE: This patch requires:
  4e63dcc Git.pm: add new temp_is_locked function
which is currently in next.

Versions v2-v3 of the "allow git-svn fetching to work using serf" patch introduced a bug when attempting to change the Git.pm _temp_cache function to use the new temp_is_locked function at the suggestion of a reviewer.

This patch reverts that change as the logic in _temp_cache isn't really conducive to using temp_is_locked because its tests are not exactly the same as the ones in temp_is_locked.

Kyle J. McKay (1):
  Git.pm: revert _temp_cache use of temp_is_locked
 perl/Git.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
-- 
1.8.3
Next: Kyle J. McKay
Message 1 of 2 in “incremental update against 'next' branch”
  1. 0/1 incremental update against 'next' branchKyle J. McKay, Jul 19, 2013
  2. 1/1 Git.pm: revert _temp_cache use of temp_is_lockedKyle J. McKay, Jul 19, 2013

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.