git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Jamey Sharp <jamey@minilop.net>,
	git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Johannes Sixt <johannes.sixt@telecom.at>,
	Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>
Subject: Re: [PATCHv4 2/4] Add infrastructure for ref namespaces
Date: Wed, 8 Jun 2011 11:41:25 +0200	[thread overview]
Message-ID: <201106081141.26994.jnareb@gmail.com> (raw)
In-Reply-To: <20110603210156.GA1806@leaf>

On Fri, 3 June 2011, Josh Triplett wrote:
> On Fri, Jun 03, 2011 at 01:35:34AM -0700, Jakub Narebski wrote:
> > Jamey Sharp <jamey@minilop.net> writes:
> > 
> > > From: Josh Triplett <josh@joshtriplett.org>
> > > 
> > > Add support for dividing the refs of a single repository into multiple
> > > namespaces, each of which can have its own branches, tags, and HEAD.
> > > Git can expose each namespace as an independent repository to pull from
> > > and push to, while sharing the object store, and exposing all the refs
> > > to operations such as git-gc.
> > [...]
> > 
> > By the way, after this feature is merged in, would you like for gitweb
> > to understand ref namespaces and offer browsing of separate namespaces
> > (sub-repositories)?
> 
> Yes, definitely!  We'd love to see gitweb handling namespaces
> transparently, and presenting them identically to top-level
> repositories.  (Also, gitweb would need to present the appropriate
> repository URIs for cloning.)

Note that for gitweb support we would need some easy way to list all
namespaces that given repository provides.  But that is for the future.

BTW. what do you think about treating repository with own refs and with
namespaces similarly to how "forks" are handled in gitweb now?
-- 
Jakub Narebski
Poland

  reply	other threads:[~2011-06-08  9:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01  0:24 [PATCHv4 1/4] Refactor for_each_ref variants to use for_each_ref_in and avoid magic numbers Jamey Sharp
2011-06-01  0:24 ` [PATCHv4 2/4] Add infrastructure for ref namespaces Jamey Sharp
2011-06-02 22:44   ` Junio C Hamano
2011-06-02 23:36     ` Josh Triplett
2011-06-03  2:51       ` Junio C Hamano
2011-06-03 17:26         ` Josh Triplett
2011-06-03  8:35   ` Jakub Narebski
2011-06-03 21:01     ` Josh Triplett
2011-06-08  9:41       ` Jakub Narebski [this message]
2011-06-09  3:38         ` Josh Triplett
2011-06-09  9:09           ` Jakub Narebski
2011-06-01  0:24 ` [PATCHv4 3/4] Support ref namespaces for remote repositories via upload-pack and receive-pack Jamey Sharp
2011-06-02 23:05   ` Junio C Hamano
2011-06-03  0:06     ` josh
2011-06-03 16:33       ` Junio C Hamano
2011-06-01  0:24 ` [PATCHv4 4/4] Add documentation for ref namespaces Jamey Sharp
2011-06-02 20:36 ` [PATCHv4 1/4] Refactor for_each_ref variants to use for_each_ref_in and avoid magic numbers Junio C Hamano
2011-06-02 20:57   ` Josh Triplett
2011-06-02 23:29     ` Junio C Hamano
2011-06-03  8:33 ` Jakub Narebski

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=201106081141.26994.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jamey@minilop.net \
    --cc=johannes.sixt@telecom.at \
    --cc=josh@joshtriplett.org \
    --cc=peff@peff.net \
    --cc=spearce@spearce.org \
    /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).