git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Derrick Stolee <derrickstolee@github.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: ds/packed-refs-v2 (was Re: What's cooking in git.git (Dec 2022, #04; Mon, 12))
Date: Mon, 12 Dec 2022 08:55:05 -0500	[thread overview]
Message-ID: <f07abb23-781b-8381-d839-ab21e725e625@github.com> (raw)
In-Reply-To: <xmqqfsdkspnl.fsf@gitster.g>

On 12/12/2022 8:43 AM, Junio C Hamano wrote:

> * ds/packed-refs-v2 (2022-11-07) 30 commits
>  - refs: skip hashing when writing packed-refs v2
>  - p1401: create performance test for ref operations
>  - ci: run GIT_TEST_PACKED_REFS_VERSION=2 in some builds
>  - t*: skip packed-refs v2 over http tests
>  - t3210: require packed-refs v1 for some tests
>  - t5502: add PACKED_REFS_V1 prerequisite
>  - t5312: allow packed-refs v2 format
>  - t1409: test with packed-refs v2
>  - packed-backend: create GIT_TEST_PACKED_REFS_VERSION
>  - packed-refs: write prefix chunks
>  - packed-refs: read optional prefix chunks
>  - packed-refs: read file format v2
>  - packed-refs: write file format version 2
>  - packed-backend: create shell of v2 writes
>  - config: add config values for packed-refs v2
>  - packed-backend: create abstraction for writing refs
>  - packed-backend: extract iterator/updates merge
>  - packed-backend: extract add_write_error()
>  - refs: extract packfile format to new file
>  - chunk-format: parse trailing table of contents
>  - chunk-format: allow trailing table of contents
>  - chunk-format: store chunk offset during write
>  - chunk-format: document trailing table of contents
>  - chunk-format: number of chunks is optional
>  - refs: allow loose files without packed-refs
>  - repository: wire ref extensions to ref backends
>  - config: fix multi-level bulleted list
>  - extensions: add refFormat extension
>  - read-cache: add index.computeHash config option
>  - hashfile: allow skipping the hash function
> 
>  Waiting for review.
>  Seems to break CI.
>  linux-TEST-vars
>  cf. https://github.com/git/git/actions/runs/3598165328
>  source: <pull.1408.git.1667846164.gitgitgadget@gmail.com>

Please eject this series. It was only an RFC on purpose, and
the first few patches have been replaced with a new series [1]
(which I will send a new version of soon)

[1] https://lore.kernel.org/git/pull.1439.git.1670433958.gitgitgadget@gmail.com/

Meanwhile, Keanen Wold and I are discussing with John Cai
about capacity around ref storage mechanisms. I also haven't
had time to do the deep-dive on reftable that I promised.

Thanks,
-Stolee

      reply	other threads:[~2022-12-12 13:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 13:43 What's cooking in git.git (Dec 2022, #04; Mon, 12) Junio C Hamano
2022-12-12 13:55 ` Derrick Stolee [this message]

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=f07abb23-781b-8381-d839-ab21e725e625@github.com \
    --to=derrickstolee@github.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.
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).