From: Elijah Newren <newren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: en/header-split-cache-h-part-2 (Was: Re: What's cooking in git.git (Apr 2023, #06; Thu, 20))
Date: Sat, 22 Apr 2023 08:00:00 -0700 [thread overview]
Message-ID: <CABPp-BHTYha8g1t5VPCkuMtgCopwx==iBGMOCxnyWpZbYMNtAQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqwn26w5cd.fsf@gitster.g>
On Thu, Apr 20, 2023 at 3:57 PM Junio C Hamano <gitster@pobox.com> wrote:
> * en/header-split-cache-h-part-2 (2023-04-18) 23 commits
> - reftable: ensure git-compat-util.h is the first (indirect) include
> - diff.h: reduce unnecessary includes
> - object-store.h: reduce unnecessary includes
> - commit.h: reduce unnecessary includes
> - fsmonitor: reduce includes of cache.h
> - cache.h: remove unnecessary headers
> - treewide: remove cache.h inclusion due to previous changes
> - cache,tree: move basic name compare functions from read-cache to tree
> - cache,tree: move cmp_cache_name_compare from tree.[ch] to read-cache.c
> - hash.h, repository.h: reverse the order of these dependencies
> - tree-diff.c: move S_DIFFTREE_IFXMIN_NEQ define from cache.h
> - dir.h: move DTYPE defines from cache.h
> - versioncmp.h: move declarations for versioncmp.c functions from cache.h
> - ws.h: move declarations for ws.c functions from cache.h
> - match-trees.h: move declarations for match-trees.c functions from cache.h
> - pkt-line.h: move declarations for pkt-line.c functions from cache.h
> - base85.h: move declarations for base85.c functions from cache.h
> - copy.h: move declarations for copy.c functions from cache.h
> - server-info.h: move declarations for server-info.c functions from cache.h
> - packfile.h: move pack_window and pack_entry from cache.h
> - symlinks.h: move declarations for symlinks.c functions from cache.h
> - treewide: be explicit about dependence on strbuf.h
> - Merge branch 'en/header-split-cache-h' into en/header-split-cache-h-part-2
> (this branch uses en/header-split-cache-h.)
>
> More header clean-up.
>
> Will merge to 'next'?
> source: <pull.1517.git.1681614205.gitgitgadget@gmail.com>
Not yet; please mark as expecting a re-roll. I need to fix up the
hash.h/repository.h patch
(https://lore.kernel.org/git/kl6lsfcu1g8w.fsf@chooglen-macbookpro.roam.corp.google.com/)
next prev parent reply other threads:[~2023-04-22 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 22:34 What's cooking in git.git (Apr 2023, #06; Thu, 20) Junio C Hamano
2023-04-21 2:16 ` tb/ban-strtok (was: Re: What's cooking in git.git (Apr 2023, #06; Thu, 20)) Taylor Blau
2023-04-22 11:22 ` Jeff King
2023-04-24 16:39 ` tb/ban-strtok Junio C Hamano
2023-04-22 15:00 ` Elijah Newren [this message]
2023-04-24 18:20 ` en/header-split-cache-h-part-2 Junio C Hamano
2023-04-22 15:00 ` pb/complete-and-document-auto-merge-and-friends (Was: Re: What's cooking in git.git (Apr 2023, #06; Thu, 20)) Elijah Newren
2023-04-22 21:53 ` Philippe Blain
2023-04-24 18:21 ` pb/complete-and-document-auto-merge-and-friends Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABPp-BHTYha8g1t5VPCkuMtgCopwx==iBGMOCxnyWpZbYMNtAQ@mail.gmail.com' \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).