git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Turner <dturner@twopensource.com>
To: Ronnie Sahlberg <sahlberg@google.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH v4 0/1] receive-pack: optionally deny case clone refs
Date: Wed, 13 Aug 2014 15:28:28 -0400	[thread overview]
Message-ID: <1407958108.9673.14.camel@leckie> (raw)
In-Reply-To: <CAL=YDW=5ynUFFLVNAG=M9x-DRyEyM2q=GPVxzxHVPYDNGHYm=A@mail.gmail.com>

On Wed, 2014-08-13 at 09:20 -0700, Ronnie Sahlberg wrote:
> David,
> 
> One possible solution can be to use the external database daemon I am
> working of for ref transactions.
> Since this makes all refs be stored in a dedicated database instead of
> the filesystem you no longer are dependent on file system semantics.
> 
> While not in the official git trees yet I would appreciate any testing
> and comments you may have it you want to test it.
> https://github.com/rsahlberg/git/tree/backend-struct-db-2
> 
> Not for production use but seeing if it does build and works on your
> platforms would be great.

Thanks. We ultimately went with a custom hook (which also enforces other
business rules), but I'm very excited about the new backend and hope it
will improve performance generally.

One thing you could do to increase adoption would be to make a Homebrew
formula for tdb. Homebrew is the defacto standard Mac packaging system.
Sadly, a large number of engineers use Macs, so this is a large barrier
-- especially since the tdb build is somewhat baroque.

It would also be great if it didn't require a fresh clone; for a large
organization with large repos, requiring every engineer to re-clone is
somewhat onerous.  I assume it's straightforward to do a conversion from
an existing set of refs but that it just hasn't been a priority for you
yet.

Thanks so much for working on this!

      reply	other threads:[~2014-08-13 19:28 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
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 [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1407958108.9673.14.camel@leckie \
    --to=dturner@twopensource.com \
    --cc=git@vger.kernel.org \
    --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).