From: Junio C Hamano <email@example.com> To: Jonathan Tan <firstname.lastname@example.org> Cc: email@example.com Subject: Re: What's cooking in git.git (Mar 2018, #03; Wed, 14) Date: Fri, 16 Mar 2018 14:52:10 -0700 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> (Jonathan Tan's message of "Fri, 16 Mar 2018 14:31:24 -0700") Jonathan Tan <firstname.lastname@example.org> writes: > On Wed, 14 Mar 2018 18:34:49 -0700 > Junio C Hamano <email@example.com> wrote: > >> * sb/object-store (2018-03-05) 27 commits > > [snip list of commits] > >> (this branch is used by sb/packfiles-in-repository; uses nd/remove-ignore-env-field.) >> >> Refactoring the internal global data structure to make it possible >> to open multiple repositories, work with and then close them. >> >> Rerolled by Duy on top of a separate preliminary clean-up topic. >> The resulting structure of the topics looked very sensible. >> >> Waiting for a follow-up discussion. > > Would it be possible for this set to go in independently of > nd/remove-ignore-env-field? I understand that some patches might be > cleaner if ignore_env is first removed, but this patch set has already > undergone several rounds of review and (I think) is an improvement to > the codebase on its own. I thought the "remove-ignore-env-field" thing is a quite small and more-or-less straightforward improvements that would serve as a good preparatory change to give a solid foundation to the object-store topic. I was hoping to hear quick Acks for remove-ignore-env (and also Duy's reroll of their topics on it) from people involved in all the related topics, so that we can advance them more-or-less at the same time.
next prev parent reply other threads:[~2018-03-16 21:52 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-15 1:34 Junio C Hamano 2018-03-15 6:30 ` Duy Nguyen 2018-03-15 16:54 ` Junio C Hamano 2018-03-15 8:36 ` Ævar Arnfjörð Bjarmason 2018-03-15 17:33 ` Junio C Hamano 2018-03-19 21:16 ` Derrick Stolee 2018-03-15 19:18 ` Lars Schneider 2018-03-15 23:00 ` Lars Schneider 2018-03-16 0:54 ` Junio C Hamano 2018-03-16 21:31 ` Jonathan Tan 2018-03-16 21:52 ` Junio C Hamano [this message] 2018-03-16 22:08 ` Jonathan Nieder 2018-03-17 0:53 ` 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 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: What'\''s cooking in git.git (Mar 2018, #03; Wed, 14)' \ /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).