From: David Turner <dturner@twopensource.com>
To: git mailing list <git@vger.kernel.org>
Cc: mhagger@alum.mit.edu
Subject: RFC/Pull request v2: Refs db backend
Date: Fri, 17 Jul 2015 17:22:00 -0400 [thread overview]
Message-ID: <1437168120.30911.9.camel@twopensource.com> (raw)
I've prepared another version of my pluggable backends series.
This version has the following changes:
1. Addressed all cosmetic review comments from previous version
2. Significant cleanup of LMDB code: formatting and variable names,
functions extracted, etc.
3. Explicit handling of per-worktree refs and pseudorefs; several new
patches in the series now address this.
4. refdb init function added to backend
5. rename of refs-be to refs-lmdb
6. Replace void * with struct ref_transaction
7. removed a memory leak
8. More documentation
9. Rebased on top of more-recent upstream (and on top of my preamble
patch series).
There are probably a few further changes that I've forgotten. Because
the patch series is 49 patches, I've made it available for pull:
https://github.com/dturner-tw/git.git on the
dturner/pluggable-backends branch
Let me know if you think it's ready for per-patch review, and I'll send
all 49 patches to the list.
Thanks.
reply other threads:[~2015-07-17 21:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1437168120.30911.9.camel@twopensource.com \
--to=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.