From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 506745fe for ; Tue, 26 Nov 2019 01:27:17 +0000 (UTC) Received: (qmail 6169 invoked by alias); 26 Nov 2019 01:27:08 -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: List-Unsubscribe: X-Seq: 44938 Received: (qmail 26244 invoked by uid 1010); 26 Nov 2019 01:27:08 -0000 X-Qmail-Scanner-Diagnostics: from mail-io1-f66.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.0/25642. spamassassin: 3.4.2. Clear:RC:0(209.85.166.66):SA:0(-2.0/5.0):. Processed in 1.729903 secs); 26 Nov 2019 01:27:08 -0000 X-Envelope-From: mezin.alexander@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.166.66 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=vAOEzFj7PJK5rvU1yt652VPRNImpNVp5nYY2Hk3qSHM=; b=DHoSRRvqtxqKZVQAp8dEEg4SU57+nZ9Cnct5lnT8uUtyead7fTyNC7QNaMWpYsGIiR zFE88YoorSSWI1OUKwHrvFa5Bz0CIp0ufwW8q2Zx3plAE/cdKU6XuQDJVJHdExD1pVP9 fqeooBrBd8rmsti10GFMZLoZ6HdD+tT7P5qrir7JS1EreLRy59zy0YXrzS6Qt4Z0IDyo SkJ5Yi9HlfCKGodb02S37bLA+DRqdW04lwg+v7J0LUXEYrryqhmJ3P5auBTHczaQzJAl En4yw/c4Hw7cyYuQJ+U+6E9mBreZkAqhmQVGNIbITWsBdZA74jleuYiE7XmImuGszcV9 cgWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=vAOEzFj7PJK5rvU1yt652VPRNImpNVp5nYY2Hk3qSHM=; b=lJvcLnxFaM9g1AIb38Vt7sswryCSLVhrKH9CAnKbh9egnO4DfZv78zQMqNcuwUCk6M nKxa2oIUDfDW5IIt5iIqmRYVy62eYAqqBcWmROhukRZIMvZRbMJL+/zLNq82Q7nrAsu4 gIf2buGeUj+iXTJ68NJn2ZKd2ZLC+atjGxU/yBj56W9p/M2Ujk2c64RmlHZUM2aRQIvh T8FByk30Y+RgfgA8Rk1db2brhJ22njcRI+Rt1dFIFvdsyPJDw1uPlrGHh5oaSqI18lO1 2/S/dMTmQFAxexGEjo9xP+kyNhy9B5yvoC/69es9L5TN/8OxJMqFT0M3totZP75XdLji gXtA== X-Gm-Message-State: APjAAAXQpouG9Q6NxZqzdg13b8uj8osGYmx6GMSxAEaKAQGuvmadwTDK 3NYLO0Wc9b5TC0SJR96XvYtpRiEwQlVSZVCiwV8= X-Google-Smtp-Source: APXvYqztTZ1T/TPm9xo0gnbRutiiZFRJNTAV92WGDB+JTHdHWhnS0ZUDtigX7g+mUGtce7R8SjuBLo45IKotk0ziQKw= X-Received: by 2002:a6b:8bcc:: with SMTP id n195mr19564307iod.135.1574731593424; Mon, 25 Nov 2019 17:26:33 -0800 (PST) MIME-Version: 1.0 References: <20191123221443.279556-1-mezin.alexander@gmail.com> <20191123221443.279556-3-mezin.alexander@gmail.com> <20191125043525.lcxm532gi6hb7n53@tarpaulin.shahaf.local2> In-Reply-To: From: Aleksandr Mezin Date: Tue, 26 Nov 2019 07:26:22 +0600 Message-ID: Subject: Re: [PATCH 2/3] vcs_info/cvs: set vcs_comm[basedir] in VCS_INFO_detect_cvs To: Daniel Shahaf Cc: zsh-workers@zsh.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Nov 25, 2019 at 2:17 PM Daniel Shahaf wrot= e: > Two, as I pointed out in reply to an offlist response, the existence of > $GIT_DIR and $GIT_WORK_TREE means that the two VCS's basedirs need not > be in a parent dir =E2=80=93 subdir relationship with each other; they ca= n be > /foo/bar and /foo/baz. How is it possible? in a git repository $ GIT_WORK_TREE=3D../other-dir git rev-parse --is-inside-work-tree false Work tree root should be a parent of cwd, otherwise `rev-parse --is-inside-work-tree` returns false -> git repository not detected. And there is only one path from cwd to the root -> all parents of cwd are parents or subdirs to each other.