From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, spearce@spearce.org, mfick@codeaurora.org
Subject: Re: [PATCH 0/2] Hiding some refs in ls-remote
Date: Sun, 20 Jan 2013 14:08:32 -0800 [thread overview]
Message-ID: <7vip6rjyn3.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vpq0zn2za.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Sun, 20 Jan 2013 10:06:33 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Jeff King <peff@peff.net> writes:
>
>>> [uploadPack]
>>> hiderefs = refs/changes
>>
>> Would you want to do the same thing on receive-pack? It could benefit
>> from the same reduction in network cost (although it tends to be invoked
>> less frequently than upload-pack).
> ...
> As I said, I view this primarily as solving the cluttering issue.
> The use of hiderefs to hide these refs that point at objects I do
> not consider belong to my repository from the pushers equally makes
> sense as such, I think.
Now that raises one question. Should this be transfer.hiderefs that
governs both upload-pack and receive-pack? I tend to think the
answer is yes.
It may even make sense to have "git push" honor it, excluding them
from "git push --mirror" (or "git push --all" if some of the
branches are hidden); I haven't thought things through, though.
next prev parent reply other threads:[~2013-01-20 22:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 0:37 [PATCH 0/2] Hiding some refs in ls-remote Junio C Hamano
2013-01-19 0:37 ` [PATCH 1/2] upload-pack: share more code Junio C Hamano
2013-01-19 0:37 ` [PATCH 2/2] upload-pack: allow hiding ref hiearchies Junio C Hamano
2013-01-19 5:50 ` [PATCH 0/2] Hiding some refs in ls-remote Duy Nguyen
2013-01-19 19:16 ` Junio C Hamano
2013-01-20 18:19 ` Junio C Hamano
2013-01-21 1:46 ` Duy Nguyen
2013-01-21 22:56 ` Jeff King
2013-01-19 6:18 ` Michael Haggerty
2013-01-19 16:50 ` Jeff King
2013-01-20 18:06 ` Junio C Hamano
2013-01-20 22:08 ` Junio C Hamano [this message]
2013-01-21 23:01 ` Jeff King
2013-01-21 23:33 ` Junio C Hamano
2013-01-21 23:45 ` Jeff King
2013-01-21 23:03 ` Jeff King
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=7vip6rjyn3.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mfick@codeaurora.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.