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

Re: [PATCH 1/6] read-cache: use sha1file for sha1 calculation

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Feb 6, 2012, 08:36 UTC
Message-ID
<CACsJy8DR2rPtC_2PDp=ZEm-3B-mzh+AxaDmXxxzJ_VY5M-0oVw@mail.gmail.com>
In-Reply-To
<7vsjio8leo.fsf@alter.siamese.dyndns.org>
2012/2/6 Junio C Hamano <gitster@pobox.com>:
> This is open source, and I wouldn't stop you from spending time on anything
> that interests you.

Well fun stuff is more interesting to do.. but I guess that's about it. More time cut down requires bigger changes that does not fit in a few hours of work.

Show 8 quoted lines
> But having said that, if you have extra Git time, I would still rather see
> you spend it first on tying up loose ends of your topics in flight and
> on helping others that touch parts that are related to areas that you have
> already thought about, namely:
>
>  (1) nd/commit-ignore-i-t-a, which I think should be marketted as fixing
>     an earlier UI mistake and presented with a clean migration path to
>     make the updated behaviour the default in the future; and

Yeah, I was avoiding the deprecation procedure (plus providing a convincing argument to push it forward). Need to look up old emails..

>  (2) the negative pathspec thing that resurfaced in disguise as Albert
>     Yale's "grep --exclude" series.
This is pure headache. Can't avoid it forever, I guess.
Show 7 quoted lines
> *1* A possible approach might be to stuff unmodified trees in the index
> without exploding them into its components, and as entries are modified,
> lazily expand these "tree" entries, while ensuring the "unmodified" parts
> remain unmodified by turning the files in the working tree read-only and
> requiring the user to say "git edit" or "git open" or something before
> starting to edit.  But as I said, I consider this not an ultra-urgent
> issue, so I haven't thought things through yet.

A sparse index is something that may be achieved with narrow clone (or narrow checkout in full clone) because by nature we can't have full index in narrow clone. That may be the right way to go.

-- 
Duy
Previous: Junio C Hamano
Message 20 of 20 in “read-cache: use sha1file for sha1 calculation”
  1. 1/6 read-cache: use sha1file for sha1 calculationNguyễn Thái Ngọc Duy, Feb 6, 2012
  2. 2/6 csum-file: make sha1 calculation optionalNguyễn Thái Ngọc Duy, Feb 6, 2012
  3. 3/6 Stop producing index version 2Nguyễn Thái Ngọc Duy, Feb 6, 2012
  4. Junio C HamanoFeb 6, 2012
  5. Shawn PearceFeb 7, 2012
  6. Nguyen Thai Ngoc DuyFeb 7, 2012
  7. Nguyen Thai Ngoc DuyFeb 7, 2012
  8. Junio C HamanoFeb 7, 2012
  9. Thomas RastFeb 7, 2012
  10. 4/6 Introduce index version 4 with global flagsNguyễn Thái Ngọc Duy, Feb 6, 2012
  11. 5/6 Allow to use crc32 as a lighter checksum on indexNguyễn Thái Ngọc Duy, Feb 6, 2012
  12. Shawn PearceFeb 7, 2012
  13. Dave ZarzyckiFeb 7, 2012
  14. Dave ZarzyckiFeb 7, 2012
  15. 6/6 Automatically switch to crc32 checksum for index when it's too largeNguyễn Thái Ngọc Duy, Feb 6, 2012
  16. Dave ZarzyckiFeb 6, 2012
  17. Nguyen Thai Ngoc DuyFeb 6, 2012
  18. Dave ZarzyckiFeb 6, 2012
  19. Junio C HamanoFeb 6, 2012
  20. Nguyen Thai Ngoc DuyFeb 6, 2012

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.