From: Thomas Rast <trast@inf.ethz.ch>
To: John Koleszar <jkoleszar@google.com>
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
<git@vger.kernel.org>, Shawn Pearce <spearce@spearce.org>,
Josh Triplett <josh@joshtriplett.org>
Subject: Re: [PATCH] http-backend: respect GIT_NAMESPACE with dumb clients
Date: Mon, 8 Apr 2013 23:25:39 +0200 [thread overview]
Message-ID: <87wqscr9yk.fsf@linux-k42r.v.cablecom.net> (raw)
In-Reply-To: <1365091293-23758-1-git-send-email-jkoleszar@google.com> (John Koleszar's message of "Thu, 4 Apr 2013 09:01:33 -0700")
John Koleszar <jkoleszar@google.com> writes:
> Filter the list of refs returned via the dumb HTTP protocol according
> to the active namespace, consistent with other clients of the
> upload-pack service.
>
> Signed-off-by: John Koleszar <jkoleszar@google.com>
At the risk of repeating something that's been said already -- I only
skimmed the thread -- this test breaks in today's pu on my machine. I
get:
expecting success: (
log_div "namespace test"
config http.uploadpack true &&
config http.getanyfile true &&
NS=ns &&
(cd "$HTTPD_DOCUMENT_ROOT_PATH/repo.git" &&
git update-ref refs/namespaces/$NS/refs/heads/master HEAD
) &&
SMART=smart
git ls-remote public >expect &&
grep /$NS/ expect &&
GET_BODY "info/refs" >actual &&
test_cmp expect actual &&
GET_BODY "info/refs?service=git-upload-pack" >actual &&
grep /$NS/ actual &&
SMART=smart_namespace &&
GIT_NAMESPACE=$NS && export GIT_NAMESPACE &&
git ls-remote public >expect &&
! grep /$NS/ expect &&
GET_BODY "info/refs" >actual &&
test_cmp expect actual &&
GET_BODY "info/refs?service=git-upload-pack" >actual &&
! grep /$NS/ actual
)
453190505bf07f7513bed9839da875eb3610f807 refs/namespaces/ns/refs/heads/master
--- expect 2013-04-08 21:24:36.571874540 +0000
+++ actual 2013-04-08 21:24:36.579874619 +0000
@@ -1,3 +1,2 @@
-453190505bf07f7513bed9839da875eb3610f807 HEAD
453190505bf07f7513bed9839da875eb3610f807 refs/heads/master
453190505bf07f7513bed9839da875eb3610f807 refs/namespaces/ns/refs/heads/master
not ok 14 - backend respects namespaces
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2013-04-08 21:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 4:58 [PATCH] http-backend: respect GIT_NAMESPACE with dumb clients John Koleszar
2013-03-28 6:02 ` Junio C Hamano
2013-03-28 15:49 ` Josh Triplett
2013-03-28 14:43 ` Junio C Hamano
[not found] ` <CAAvHm8NAqVHLz1wjNN-3ocpYzWfO-PDo0PAJ6pZO7KrMkhJ6Jw@mail.gmail.com>
2013-03-28 15:54 ` John Koleszar
2013-03-28 16:46 ` Junio C Hamano
2013-04-03 15:52 ` John Koleszar
2013-04-03 16:10 ` Jeff King
2013-04-03 16:16 ` Jeff King
2013-04-03 18:05 ` Junio C Hamano
2013-04-04 15:34 ` John Koleszar
2013-04-04 16:01 ` John Koleszar
2013-04-04 17:25 ` Junio C Hamano
2013-04-05 1:22 ` John Koleszar
2013-04-05 2:35 ` Josh Triplett
2013-04-05 2:56 ` Jeff King
2013-04-05 5:34 ` Junio C Hamano
2013-04-05 5:43 ` Jeff King
2013-04-06 0:54 ` John Koleszar
2013-04-10 0:55 ` [PATCH v4] " John Koleszar
2013-04-10 1:09 ` Junio C Hamano
2013-04-10 4:18 ` Jeff King
2013-04-08 21:25 ` Thomas Rast [this message]
2013-04-08 21:45 ` [PATCH] " Jeff King
2013-04-09 22:13 ` John Koleszar
2013-04-03 18:04 ` 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=87wqscr9yk.fsf@linux-k42r.v.cablecom.net \
--to=trast@inf.ethz.ch \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jkoleszar@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.