git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Josh Triplett <josh@joshtriplett.org>,
	Jamey Sharp <jamey@minilop.net>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Jakub Narebski <jnareb@gmail.com>,
	Bert Wesarg <bert.wesarg@googlemail.com>,
	git@vger.kernel.org
Subject: Re: [PATCHv3] ref namespaces: tests
Date: Fri, 22 Jul 2011 16:32:13 -0600	[thread overview]
Message-ID: <20110722223211.GA19620@sigill.intra.peff.net> (raw)
In-Reply-To: <7v62mux9ae.fsf@alter.siamese.dyndns.org>

On Thu, Jul 21, 2011 at 02:56:16PM -0700, Junio C Hamano wrote:

> Josh Triplett <josh@joshtriplett.org> writes:
> 
> > At this point I think we've incorporated all the outstanding feedback.
> > Does this test need any further changes to allow the ref-namespaces
> > branch to graduate to next?
> 
> No more nitpicks from me on this patch at least for now.
> 
> Are people who expressed concern during the review on the previous round
> of the series happy with the second round? I recall there was a strong
> sentiment that it is regrettable that the series specifically changes
> fetch and push and is not a more general mechanism. Personally I am OK
> with the approach taken by this series, as I do not offhand think of other
> ways to serve a modified namespace. You have to view the unaltered reality
> when interacting with your own refs to enumerate the objects you have,
> while giving the altered view to your clients that is limited to the
> "virtual" space.

I was one of the people who wanted to have namespaces or virtual repos
at a more fundamental level. However, I tried to do a relatively simple
patch when the discussion started, and ended up getting mired in corner
cases. And it sounds like Josh and Jamey made a good faith effort in
that direction, but still ended up where they are now. So I'm willing to
accept that it is not as simple as we hoped, and the more practical
approach from their series is acceptable.

As for the code itself, I admit I haven't been paying all that close
attention. I can try to give a more careful review if we want another
set of eyes.

-Peff

  reply	other threads:[~2011-07-22 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-14 20:50 [PATCH] ref namespaces: tests Josh Triplett
2011-07-14 23:13 ` Junio C Hamano
2011-07-15  3:45   ` Josh Triplett
2011-07-15 18:40     ` [PATCHv2] " Josh Triplett
2011-07-21 20:10       ` [PATCHv3] " Josh Triplett
2011-07-21 21:56         ` Junio C Hamano
2011-07-22 22:32           ` Jeff King [this message]
2011-07-15 19:37   ` [PATCH] " Junio C Hamano

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=20110722223211.GA19620@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=bert.wesarg@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jamey@minilop.net \
    --cc=jnareb@gmail.com \
    --cc=josh@joshtriplett.org \
    --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).