From: Junio C Hamano <gitster@pobox.com>
To: Antoine Pelisse <apelisse@gmail.com>
Cc: "Jörn Hees" <dev@joernhees.de>, git <git@vger.kernel.org>,
"Felipe Contreras" <felipe.contreras@gmail.com>
Subject: Re: [PATCH] [SIGNED-OFF] remotes-hg: bugfix for fetching non local remotes
Date: Wed, 24 Jul 2013 08:20:47 -0700 [thread overview]
Message-ID: <7v7ggg6l2o.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CALWbr2wDqo29kRJ2eHsozRCN_fT3tumYz23pQa5P-9dm27OL6A@mail.gmail.com> (Antoine Pelisse's message of "Wed, 24 Jul 2013 15:14:03 +0200")
Antoine Pelisse <apelisse@gmail.com> writes:
> On Wed, Jul 24, 2013 at 11:59 AM, Jörn Hees <dev@joernhees.de> wrote:
>> On 24.07.2013, at 10:52, Antoine Pelisse <apelisse@gmail.com> wrote:
>>> I think the best way would be to create the shared repository in
>>> .git/hg/$share, with $share being a path that can't be a remote name
>>> (so that it doesn't conflict with remote directories),
>>
>> Maybe ".git/hg/.share"?
>
> According to Documentation/git-check-ref-format.txt, I'm not sure if
> we should start with a dot, or end with it.
What are in these directories under .git/hg? Surely they cannot be
refs in Git's sense, as that hierarchy is not known to anything and
will not be protected from "git gc".
Puzzled...
Goes and looks...
OK, the tracking branches for these are created under refs/hg/*
using the same name.
A refname shouldn't begin or end with a dot, because the range
master...share
will become ambiguous if you allowed ".share" as a refname
shorthand. It could mean either one of these:
master..refs/heads/.share
master...refs/heads/share
The same for the trailing dot "share."; the range "share...master"
becomes ambiguous.
next prev parent reply other threads:[~2013-07-24 15:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 21:40 [PATCH] [SIGNED-OFF] remotes-hg: bugfix for fetching non local remotes Joern Hees
2013-07-24 8:52 ` Antoine Pelisse
2013-07-24 9:59 ` Jörn Hees
2013-07-24 13:14 ` Antoine Pelisse
2013-07-24 14:21 ` Jörn Hees
2013-07-24 15:20 ` Junio C Hamano [this message]
2013-07-24 15:28 ` Jörn Hees
2013-07-24 22:51 ` Junio C Hamano
2013-07-25 19:30 ` Felipe Contreras
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=7v7ggg6l2o.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=apelisse@gmail.com \
--cc=dev@joernhees.de \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.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.
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).