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

What's cooking in git.git (topics)

From
Junio C Hamano <junkio@cox.net>
Date
Feb 14, 2007, 23:59 UTC
Message-ID
<7vhctojnof.fsf@assigned-by-dhcp.cox.net>

Here are the topics that have been cooking. Commits prefixed with '-' are only in 'pu' while commits prefixed with '+' are in 'next'. The topics list the commits in reverse chronological order.

* lt/crlf (Wed Feb 14 14:54:00 2007 -0800) 3 commits
 + t0020: add test for auto-crlf
 + Make AutoCRLF ternary variable.
 + Lazy man's auto-CRLF

I suspect this has quite a long way to go, since the code to do stacked .gitignore is tightly coupled with the directory walking code, and the proposed .gitattribute needs to redo that logic; which hopefully would result in nicer code that can then be used for handing .gitignore -- so we'll all win. I think git-apply codepath needs to be fixed independently from what Linus already did, but I haven't looked into it deeply yet.

* ap/cvsserver (Tue Feb 13 15:12:45 2007 +0000) 1 commit
 + Have git-cvsserver call hooks/update before really altering the
   ref

This I think is Ok. Just waiting for Acks from third-party git-cvsserver users.

* jc/fetch (Tue Feb 13 01:21:41 2007 +0000) 8 commits
 - Use stdin reflist passing in git-fetch.sh
 - Use stdin reflist passing in parse-remote
 - Allow fetch--tool to read from stdin
 - git-fetch: rewrite expand_ref_wildcard in C
 - git-fetch: rewrite another shell loop in C
 - git-fetch: move more code into C.
 - git-fetch--tool: start rewriting parts of git-fetch in C.
 - git-fetch: split fetch_main into fetch_dumb and fetch_native

Stalled. I think the subroutines in git-fetch--tool are reusable for rewriting git-fetch entirely in C, but I estimate I've covered only 30% or so of what is necessary.

* jc/diff (Mon Dec 25 01:08:50 2006 -0800) 2 commits
 - test-para: combined diff between HEAD, index and working tree.
 - para-walk: walk n trees, index and working tree in parallel
Stalled.
Message 1 of 1 in “What's cooking in git.git (topics)”
  1. Junio C HamanoFeb 14, 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.