From: Stefan Beller <sbeller@google.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Apr 2018, #01; Mon, 9)
Date: Mon, 9 Apr 2018 10:23:49 -0700 [thread overview]
Message-ID: <CAGZ79kYECaGUvHscsDaT_pzBLdRaO0E34275UsxM4LMW1Ykt7g@mail.gmail.com> (raw)
In-Reply-To: <CACsJy8C4GUy1xv10oQyrDVkdy4nq636N24b2_pGo-nivPY-x=A@mail.gmail.com>
On Mon, Apr 9, 2018 at 8:31 AM, Duy Nguyen <pclouds@gmail.com> wrote:
> On Mon, Apr 9, 2018 at 12:21 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> * sb/packfiles-in-repository (2018-03-26) 12 commits
>> (merged to 'next' on 2018-03-30 at caa68db14d)
>> + packfile: keep prepare_packed_git() private
>> + packfile: allow find_pack_entry to handle arbitrary repositories
>> + packfile: add repository argument to find_pack_entry
>> + packfile: allow reprepare_packed_git to handle arbitrary repositories
>> + packfile: allow prepare_packed_git to handle arbitrary repositories
>> + packfile: allow prepare_packed_git_one to handle arbitrary repositories
>> + packfile: add repository argument to reprepare_packed_git
>> + packfile: add repository argument to prepare_packed_git
>> + packfile: add repository argument to prepare_packed_git_one
>> + packfile: allow install_packed_git to handle arbitrary repositories
>> + packfile: allow rearrange_packed_git to handle arbitrary repositories
>> + packfile: allow prepare_packed_git_mru to handle arbitrary repositories
>> (this branch uses nd/remove-ignore-env-field and sb/object-store; is tangled with sb/submodule-move-nested.)
>>
>> Refactoring of the internal global data structure continues.
>>
>> Is this ready for 'master' by now?
>
> I think so. Things start to look much nicer.
I think so, too.
I am working on top of that series now for the third part,
assuming this is good to go.
https://public-inbox.org/git/20180406232136.253950-1-sbeller@google.com/
Thanks,
Stefan
next prev parent reply other threads:[~2018-04-09 17:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 10:21 What's cooking in git.git (Apr 2018, #01; Mon, 9) Junio C Hamano
2018-04-09 13:37 ` Derrick Stolee
2018-04-09 16:49 ` Ramsay Jones
2018-04-09 22:08 ` Junio C Hamano
2018-04-10 12:57 ` Derrick Stolee
2018-04-10 19:12 ` Stefan Beller
2018-04-10 19:21 ` Ramsay Jones
2018-04-10 19:21 ` Ramsay Jones
2018-04-10 19:35 ` Derrick Stolee
2018-04-10 20:22 ` Ramsay Jones
2018-04-10 20:37 ` Ramsay Jones
2018-04-10 21:46 ` Junio C Hamano
2018-04-09 15:31 ` Duy Nguyen
2018-04-09 17:23 ` Stefan Beller [this message]
2018-04-09 20:14 ` Johannes Schindelin
2018-04-09 21:32 ` Johannes Schindelin
2018-04-10 12:25 ` Johannes Schindelin
2018-04-10 21:02 ` git-gui branches, was " Johannes Schindelin
2018-04-10 21:38 ` Junio C Hamano
2018-04-10 21:54 ` Stefan Beller
2018-04-10 22:41 ` Johannes Schindelin
2018-04-11 10:13 ` Phillip Wood
2018-04-11 18:47 ` Jakub Narebski
2018-04-11 20:51 ` Ævar Arnfjörð Bjarmason
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=CAGZ79kYECaGUvHscsDaT_pzBLdRaO0E34275UsxM4LMW1Ykt7g@mail.gmail.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.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.
Code repositories for project(s) associated with this public 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).