From: David Turner <dturner@twopensource.com>
To: Ronnie Sahlberg <sahlberg@google.com>
Cc: Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
Michael Haggerty <mhagger@alum.mit.edu>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH v4 0/1] receive-pack: optionally deny case clone refs
Date: Sun, 15 Jun 2014 03:10:40 -0400 [thread overview]
Message-ID: <1402816240.5629.83.camel@stross> (raw)
In-Reply-To: <CAL=YDWnHubbC3eOUjHtbiddG0HiaNUW13=GRMXKfyxB+Yomq_g@mail.gmail.com>
On Fri, 2014-06-13 at 12:05 -0700, Ronnie Sahlberg wrote:
> Thinking about it more.
>
> I think we want to wait until the ref transaction API work is
> finished. The ref transactions API is in progress and it aims to add
> transactions for ref updates as a first step but then it aims to
> define a public API for all public ref functions. As part of that I
> will also develop support for pluggable ref backends. The first
> backend will be the current files based structure but I also will add
> an optional backend using a TDB database.
OK, in that case I'll shelve this patch for now (except that we'll
probably use it internally) If for some reason pluggable ref backends
don't work out, we can always revive it.
Thanks to all for the reviews. You can find the latest version at
https://github.com/dturner-tw/git/tree/case-ref .
next prev parent reply other threads:[~2014-06-15 7:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 22:30 [PATCH v4 0/1] receive-pack: optionally deny case clone refs David Turner
2014-06-11 22:30 ` [PATCH v4 1/1] " David Turner
2014-06-13 4:03 ` Torsten Bögershausen
2014-06-12 19:47 ` [PATCH v4 0/1] " Junio C Hamano
2014-06-12 23:30 ` David Turner
2014-06-13 4:03 ` Torsten Bögershausen
2014-06-13 17:12 ` Junio C Hamano
2014-06-13 17:08 ` Junio C Hamano
2014-06-13 18:20 ` Ronnie Sahlberg
2014-06-13 19:05 ` Ronnie Sahlberg
2014-06-13 21:11 ` Junio C Hamano
2014-06-13 22:24 ` Ronnie Sahlberg
2014-06-15 7:10 ` David Turner [this message]
2014-06-13 21:25 ` Junio C Hamano
2014-06-18 11:33 ` Michael Haggerty
2014-06-18 15:03 ` Ronnie Sahlberg
2014-08-13 16:20 ` Ronnie Sahlberg
2014-08-13 19:28 ` David Turner
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=1402816240.5629.83.camel@stross \
--to=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=mhagger@alum.mit.edu \
--cc=sahlberg@google.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).