git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Richard Maw <richard.maw@gmail.com>
Cc: git@vger.kernel.org, Michael Haggerty <mhagger@alum.mit.edu>
Subject: Re: [RFC PATCH 0/7] Implement ref namespaces as a ref storage backend
Date: Tue, 15 Aug 2017 10:13:22 -0700	[thread overview]
Message-ID: <xmqqefscsqj1.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170813193611.4233-1-richard.maw@gmail.com> (Richard Maw's message of "Sun, 13 Aug 2017 20:36:04 +0100")

Richard Maw <richard.maw@gmail.com> 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 starting point.

Yeah, I also made an ultra-brief foray into ref backends a few weeks
ago, and found that Michael did an excellent job identifying the
building blocks backends may want to implement differently and
abstracting out major parts of the ref processing.  I also hit some
of the same issues you mention, e.g. "HEAD" and other funny refs.

I do suspect that the current GIT_NAMESPACE thing may have outlived
its usefulness and with the pluggable ref backend thing in place, we
may want to redesign how support for multiple views into the same
repository is done.  I do not have a need for such a thing myself,
but I am glad somebody is looking into it ;-)


  parent reply	other threads:[~2017-08-15 17:13 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 ` [RFC PATCH 0/7] Implement ref namespaces as a ref storage backend Stefan Beller
2017-08-15 17:13 ` Junio C Hamano [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=xmqqefscsqj1.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=mhagger@alum.mit.edu \
    --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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).