From: Duy Nguyen <email@example.com> To: Thomas Gummerer <firstname.lastname@example.org> Cc: Git Mailing List <email@example.com>, Thomas Rast <firstname.lastname@example.org>, Michael Haggerty <email@example.com>, Junio C Hamano <firstname.lastname@example.org>, Robin Rosenberg <email@example.com> Subject: Re: [PATCH 5.5/22] Add documentation for the index api Date: Thu, 11 Jul 2013 18:42:06 +0700 [thread overview] Message-ID: <CACsJy8DNQ5Sr4a7PZMX4G-pf+fHqR398b3mncCZtQ-BBBpD+RQ@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Thu, Jul 11, 2013 at 6:30 PM, Thomas Gummerer <email@example.com> wrote: > Duy Nguyen <firstname.lastname@example.org> writes: > >> On Wed, Jul 10, 2013 at 3:10 AM, Thomas Gummerer <email@example.com> wrote: >>>> If you happen to know that certain entries match the given pathspec, >>>> you could help the caller avoid match_pathspec'ing again by set a bit >>>> in ce_flags. >>> >>> I currently don't know which entries do match the pathspec from just >>> reading the index file, additional calls would be needed. I don't think >>> that would be worth the overhead. >> >> Yeah I now see that you select what to load in v5 with the adjusted >> pathspec, not the input pathspec. Originally I thought you match the >> input pathspec against every file entry in the index :P Your adjusted >> pathspec looks like what common_prefix is for. It's cheaper than >> creating adjusted_pathspec from match_pathspec and reduces loading in >> major cases, where glob is not used. >> >> Still, creating an adjusted pathspec this way looks iffy. You need to >> understand pathspec in order to strip the filename part out to match >> the directory match only. An alternative is use >> tree_entry_interesting. It goes along well with tree traversal and can >> be used to match directories with original pathspec. Once you see it >> matches an entry in a directory, you could skip matching the rest of >> the files and load the whole directory. read_index_filtered_v5 and >> read_entries may need some tweaking though. I'll try it and post a >> patch later if I succeed. > > Hrm, I played around a bit with this idea, but I couldn't figure out how > to make it work. For it to work we would still have to load some > entries in a directory at least? Or is there a way to match the > directories, which I just haven't figured out yet? Yes you have to load some entries first. Even if a directory does not match, we only know until at least the first file in the directory. OK there might be problems because tree_entry_interesting expects all entries in a directory to be memcmp sorted, without trailing slash for subdirectories. I need to check again if v5 sort order is compatible.. -- Duy
next prev parent reply other threads:[~2013-07-11 11:42 UTC|newest] Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-07 8:11 [PATCH 00/22] Index v5 Thomas Gummerer 2013-07-07 8:11 ` [PATCH 01/22] t2104: Don't fail for index versions other than  Thomas Gummerer 2013-07-07 8:11 ` [PATCH 02/22] read-cache: split index file version specific functionality Thomas Gummerer 2013-07-07 8:11 ` [PATCH 03/22] read-cache: move index v2 specific functions to their own file Thomas Gummerer 2013-07-07 8:11 ` [PATCH 04/22] read-cache: Re-read index if index file changed Thomas Gummerer 2013-07-07 8:11 ` [PATCH 05/22] read-cache: add index reading api Thomas Gummerer 2013-07-08 2:01 ` Duy Nguyen 2013-07-08 11:40 ` Thomas Gummerer 2013-07-08 2:19 ` Duy Nguyen 2013-07-08 11:20 ` Thomas Gummerer 2013-07-08 12:45 ` Duy Nguyen 2013-07-08 13:37 ` Thomas Gummerer 2013-07-08 20:54 ` [PATCH 5.5/22] Add documentation for the index api Thomas Gummerer 2013-07-09 15:42 ` Duy Nguyen 2013-07-09 20:10 ` Thomas Gummerer 2013-07-10 5:28 ` Duy Nguyen 2013-07-11 11:30 ` Thomas Gummerer 2013-07-11 11:42 ` Duy Nguyen [this message] 2013-07-11 12:27 ` Duy Nguyen 2013-07-08 16:36 ` [PATCH 05/22] read-cache: add index reading api Junio C Hamano 2013-07-08 20:10 ` Thomas Gummerer 2013-07-08 23:09 ` Junio C Hamano 2013-07-09 20:13 ` Thomas Gummerer 2013-07-07 8:11 ` [PATCH 06/22] make sure partially read index is not changed Thomas Gummerer 2013-07-08 16:31 ` Junio C Hamano 2013-07-08 18:33 ` Thomas Gummerer 2013-07-07 8:11 ` [PATCH 07/22] dir.c: use index api Thomas Gummerer 2013-07-07 8:11 ` [PATCH 08/22] tree.c: " Thomas Gummerer 2013-07-07 8:11 ` [PATCH 09/22] name-hash.c: " Thomas Gummerer 2013-07-07 8:11 ` [PATCH 10/22] grep.c: Use " Thomas Gummerer 2013-07-07 8:11 ` [PATCH 11/22] ls-files.c: use the " Thomas Gummerer 2013-07-07 8:11 ` [PATCH 12/22] read-cache: make read_blob_data_from_index use " Thomas Gummerer 2013-07-07 8:11 ` [PATCH 13/22] documentation: add documentation of the index-v5 file format Thomas Gummerer 2013-07-11 10:39 ` Duy Nguyen 2013-07-11 11:39 ` Thomas Gummerer 2013-07-11 11:47 ` Duy Nguyen 2013-07-11 12:26 ` Thomas Gummerer 2013-07-11 12:50 ` Duy Nguyen 2013-07-07 8:11 ` [PATCH 14/22] read-cache: make in-memory format aware of stat_crc Thomas Gummerer 2013-07-07 8:11 ` [PATCH 15/22] read-cache: read index-v5 Thomas Gummerer 2013-07-07 20:18 ` Eric Sunshine 2013-07-08 11:40 ` Thomas Gummerer 2013-07-07 8:11 ` [PATCH 16/22] read-cache: read resolve-undo data Thomas Gummerer 2013-07-07 8:11 ` [PATCH 17/22] read-cache: read cache-tree in index-v5 Thomas Gummerer 2013-07-07 20:41 ` Eric Sunshine 2013-07-07 8:11 ` [PATCH 18/22] read-cache: write index-v5 Thomas Gummerer 2013-07-07 20:43 ` Eric Sunshine 2013-07-07 8:11 ` [PATCH 19/22] read-cache: write index-v5 cache-tree data Thomas Gummerer 2013-07-07 8:11 ` [PATCH 20/22] read-cache: write resolve-undo data for index-v5 Thomas Gummerer 2013-07-07 8:11 ` [PATCH 21/22] update-index.c: rewrite index when index-version is given Thomas Gummerer 2013-07-07 8:12 ` [PATCH 22/22] p0003-index.sh: add perf test for the index formats Thomas Gummerer
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CACsJy8DNQ5Sr4a7PZMX4G-pf+fHqR398b3mncCZtQ-BBBpD+RQ@mail.gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 5.5/22] Add documentation for the index api' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).