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

Re: What's cooking in git.git (Jun 2014, #01; Tue, 3)

From
Jens Lehmann <jens.lehmann@web.de>
Date
Jun 4, 2014, 19:15 UTC
Message-ID
<538F7050.3040103@web.de>
In-Reply-To
<xmqqzjhtvdua.fsf@gitster.dls.corp.google.com>
Am 04.06.2014 00:16, schrieb Junio C Hamano:
Show 9 quoted lines
> * jl/status-added-submodule-is-never-ignored (2014-04-07) 2 commits
>  - commit -m: commit staged submodules regardless of ignore config
>  - status/commit: show staged submodules regardless of ignore config
> 
>  There also are a few patches Ronald Weiss and Jens are working on
>  polishing around this topic, and a patch from Jens each for gitk
>  and git-gui.
> 
>  Waiting for the dust to settle until picking them up all.

To me it looks like the dust settled enough around that part of the topic and I remember consensus about that change. But it would be nice to have the gitk and git-gui patches in at the same time.

Show 9 quoted lines
> * jl/submodule-recursive-checkout (2013-12-26) 5 commits
>  - Teach checkout to recursively checkout submodules
>  - submodule: teach unpack_trees() to update submodules
>  - submodule: teach unpack_trees() to repopulate submodules
>  - submodule: teach unpack_trees() to remove submodule contents
>  - submodule: prepare for recursive checkout of submodules
> 
>  An RFCv2 exists ($gmane/241455) with sizable review comments.
>  Expecting a reroll.

Will do, but only after I rerolled the submodule test harness ($gmane/245048) soonish, as I intend to reuse the infrastructure introduced there for tests.

> * jh/submodule-tests (2014-04-17) 1 commit
>  - t7410: 210 tests for various 'git submodule update' scenarios

Will look deeper into that one in the next days, we really need more test coverage in that area.

Previous: Richard HansenNext: Junio C Hamano
Message 3 of 5 in “What's cooking in git.git (Jun 2014, #01; Tue, 3)”
  1. Junio C HamanoJun 3, 2014
  2. Richard HansenJun 3, 2014
  3. Jens LehmannJun 4, 2014
  4. Junio C HamanoJun 4, 2014
  5. Jens LehmannJun 4, 2014

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.