From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26083 invoked by alias); 16 Jan 2014 14:43:45 -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: 32263 Received: (qmail 26170 invoked from network); 16 Jan 2014 14:43:41 -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=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= benjamin-peterson.org; h=message-id:from:to:cc:mime-version :content-transfer-encoding:content-type:subject:date; s=mesmtp; bh=+jEO83SRRCpy15zeVOdIB9aiYDg=; b=f2UX9FhGa81Pkz6GCM+w0fiBQ3R8 09jrVr1zQND8WSTx9kpSDcotDdQefYVwDXj9qrrhkA5HpY6lB6NuYsUau+ZWranI P/D++PPSHh33ri4gUap5ztqXiwYMMnR134rm6WpV8zbnrCvr3mFzw9/EJnTsclGB VmyjABVfHeXIpg4= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:cc:mime-version :content-transfer-encoding:content-type:subject:date; s=smtpout; bh=+jEO83SRRCpy15zeVOdIB9aiYDg=; b=hbFeYpl11BtrBjGhlnIrXFj91O9F envmzcLgnFQbyOVc7F3vKhnmVOxVw6ibSE59Juru35ANHlfW3XUcHmSlKoZgGPnk Ew55eumREV/2n6Jko8RkQplQr8MqLN2QAgd0wJTRNRWlIk1+Jh9tAIAAztIfdk5Y UCl67HRKRL0EL7s= Message-Id: <1389883420.25044.71559021.17BA51C0@webmail.messagingengine.com> X-Sasl-Enc: fCbBSw8t+wNOf+hhDSRpRUunqmyxl14kZHmXE+Q5o74s 1389883420 From: Benjamin Peterson To: Frank Terbeck Cc: zsh-workers@zsh.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-fdd84f42 Subject: Re: vcs_info for mercurial doesn't detect shared repos Date: Thu, 16 Jan 2014 06:43:40 -0800 On Thu, Jan 16, 2014, at 01:14 AM, Frank Terbeck wrote: > We used to use =E2=80=98branch=E2=80=99 as the file to check for but move= d 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). >=20 > 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. I see. Tricky! >=20 > If a mercurial developer has an idea on how to properly detect this > particular extension, I'd be all ears. ;) shared repos have a file .hg/sharedpath if that helps -- Regards, Benjamin