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

[PATCH 0/5] nd/fix-sparse-checkout v2

From
Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Date
Jul 31, 2010, 06:14 UTC
Message-ID
<1280556869-707-1-git-send-email-pclouds@gmail.com>

Discussion of patch 1/3 from the first series resulted in 2/5 in this series. 2/3 and 3/3 from the former have commit messages revised, code change remains the same.

Jonathan Nieder (1):
  t1011 (sparse checkout): style nitpicks
Nguyễn Thái Ngọc Duy (4):
  unpack-trees: only clear CE_UPDATE|CE_REMOVE when skip-worktree is always set
  unpack-trees: let read-tree -u remove index entries outside sparse area
  unpack-trees: do not check for conflict entries too early
  unpack-trees: mark new entries skip-worktree appropriately
 cache.h                              |    3 +-
 t/t1011-read-tree-sparse-checkout.sh |  123 +++++++++++++++++++++-------------
 unpack-trees.c                       |   56 +++++++++-------
 3 files changed, 108 insertions(+), 74 deletions(-)
Next: Nguyễn Thái Ngọc Duy
Message 1 of 10 in “nd/fix-sparse-checkout v2”
  1. 0/5 nd/fix-sparse-checkout v2Nguyễn Thái Ngọc Duy, Jul 31, 2010
  2. 1/5 t1011 (sparse checkout): style nitpicksNguyễn Thái Ngọc Duy, Jul 31, 2010
  3. Junio C HamanoAug 2, 2010
  4. Junio C HamanoAug 2, 2010
  5. 2/5 unpack-trees: only clear CE_UPDATE|CE_REMOVE when skip-worktree is always setNguyễn Thái Ngọc Duy, Jul 31, 2010
  6. Jonathan NiederAug 8, 2010
  7. 3/5 unpack-trees: let read-tree -u remove index entries outside sparse areaNguyễn Thái Ngọc Duy, Jul 31, 2010
  8. 4/5 unpack-trees: do not check for conflict entries too earlyNguyễn Thái Ngọc Duy, Jul 31, 2010
  9. 5/5 unpack-trees: mark new entries skip-worktree appropriatelyNguyễn Thái Ngọc Duy, Jul 31, 2010
  10. Jonathan NiederAug 3, 2010

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.