From: Stefan Beller <sbeller@google.com>
To: Richard Maw <richard.maw@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [RFC PATCH 0/7] Implement ref namespaces as a ref storage backend
Date: Mon, 14 Aug 2017 10:00:09 -0700 [thread overview]
Message-ID: <CAGZ79kZz16kwwMOxoi+6UksT2CaPBU5O+r3QzxfrUBf8c3whhg@mail.gmail.com> (raw)
In-Reply-To: <20170813193611.4233-1-richard.maw@gmail.com>
> Technical description
> =====================
>
> This patch series adds a new refs backend, stacking on top of the files backend,
> based on whether `core.namespace` is set in git config.
Currently there is another Big Thing getting started in in the refs backend.
https://public-inbox.org/git/CAJo=hJtg0PAVHT1phbArdra8+4LfnEEuaj3fBid==BXkZghi8g@mail.gmail.com/
Maybe it is worth looking into that as well? Reftables solve
the problem of scaling (i.e. a repo containing a million refs works
just fine, and fast(!) for reading/writing refs, which is not the case
for packed refs)
next prev parent reply other threads:[~2017-08-14 17:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-13 19:36 [RFC PATCH 0/7] Implement ref namespaces as a ref storage backend Richard Maw
2017-08-13 19:36 ` [PATCH 1/7] Expose expand_namespace API Richard Maw
2017-08-13 19:36 ` [PATCH 2/7] Add git_configset_add_standard Richard Maw
2017-08-13 19:36 ` [PATCH 3/7] Add helper for skipping namespace prefixes Richard Maw
2017-08-13 19:36 ` [PATCH 4/7] Autocreate reflogs for namespaced refs Richard Maw
2017-08-13 19:36 ` [PATCH 5/7] Treat namespaced HEAD and refs/bisect as per-worktree Richard Maw
2017-08-13 19:36 ` [PATCH 6/7] Add namespaced ref backend Richard Maw
2017-08-13 19:36 ` [PATCH 7/7] Plumb in namespaced ref store Richard Maw
2017-08-14 17:00 ` Stefan Beller [this message]
2017-08-15 17:13 ` [RFC PATCH 0/7] Implement ref namespaces as a ref storage backend Junio C Hamano
2017-08-24 10:20 ` Richard Maw
2017-08-24 16:17 ` Michael Haggerty
2017-08-30 13:17 ` Richard Maw
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=CAGZ79kZz16kwwMOxoi+6UksT2CaPBU5O+r3QzxfrUBf8c3whhg@mail.gmail.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=richard.maw@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.
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 NNTP newsgroup(s).