From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28263 invoked by alias); 16 Jan 2014 09:21:24 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 32260 Received: (qmail 15140 invoked from network); 16 Jan 2014 09:21:18 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE, SPF_HELO_PASS autolearn=ham version=3.3.2 From: Frank Terbeck To: Benjamin Peterson Cc: zsh-workers@zsh.org Subject: Re: vcs_info for mercurial doesn't detect shared repos In-Reply-To: <1389837583.24091.71345781.48879D2E@webmail.messagingengine.com> (Benjamin Peterson's message of "Wed, 15 Jan 2014 17:59:43 -0800") References: <1389837583.24091.71345781.48879D2E@webmail.messagingengine.com> User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3.50 (gnu/linux) Organisation: 63797068657270756e6b Date: Thu, 16 Jan 2014 10:14:49 +0100 Message-ID: <87ha94b852.fsf@ft.bewatermyfriend.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Df-Sender: NDMwNDQ0 Benjamin Peterson wrote: > Hi, Hey! > The hg share extension [1] lets you have multiple working trees with > with the same backing repository. It seems vcs_info fails to detect > working copies where the share extension is used because those .hg dirs > don't contain "store" or "data" subdirectories as the VCS detection > requires. It think it would be safer to look for the "hgrc" or "branch" > file. We used to use =E2=80=98branch=E2=80=99 as the file to check for but moved = away from it, because it didn't work reliably with newer versions of mercurial (this might have changed again in the meantime, since I don't follow mercurial's development too closely). Checking for =E2=80=98hgrc=E2=80=99 is not an option, because ~/.hg/hgrc is= a possible configuration file location, which would lead to false positives in the user's home directory. If a mercurial developer has an idea on how to properly detect this particular extension, I'd be all ears. ;) Regards, Frank --=20 In protocol design, perfection has been reached not when there is nothing left to add, but when there is nothing left to take away. -- RFC 1925