On Thu, Aug 24, 2017 at 06:17:07PM +0200, Michael Haggerty wrote:
> On Sun, Aug 13, 2017 at 9:36 PM, Richard Maw wrote:
> > [...]
> > Fortunately the pluggable ref backends work provided an easier starting
> > point.
>
> :-) I'm glad my years-long obsession is finally yielding fruit.
>
> First
On Sun, Aug 13, 2017 at 9:36 PM, Richard Maw wrote:
> Forewarning: I don't consider this work complete
> and am unlikely to find time to finish it any time soon.
> I've mostly sent this because it may include valuable feedback
> on how well the ref storage backends works
> from trying to use it to
On Tue, Aug 15, 2017 at 10:13:22AM -0700, Junio C Hamano wrote:
> Richard Maw writes:
>
> > This is not my first attempt to improve the git namespace handling in git.
> > I tried last year, but it took me so long that all the ref handling code
> > changed
> > and I would have had to start from s
Richard Maw writes:
> This is not my first attempt to improve the git namespace handling in git.
> I tried last year, but it took me so long that all the ref handling code
> changed
> and I would have had to start from scratch.
>
> Fortunately the pluggable ref backends work provided an easier s
> 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/gi
Forewarning: I don't consider this work complete
and am unlikely to find time to finish it any time soon.
I've mostly sent this because it may include valuable feedback
on how well the ref storage backends works
from trying to use it to change how git namespaces work.
Introduction
I
6 matches
Mail list logo
