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=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, 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 921930b8 for ; Mon, 25 Nov 2019 09:14:17 +0000 (UTC) Received: (qmail 4957 invoked by alias); 25 Nov 2019 09:14:11 -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: 44931 Received: (qmail 4802 invoked by uid 1010); 25 Nov 2019 09:14:11 -0000 X-Qmail-Scanner-Diagnostics: from mail-lj1-f193.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.208.193):SA:0(-1.9/5.0):. Processed in 1.768688 secs); 25 Nov 2019 09:14:11 -0000 X-Envelope-From: schaefer@brasslantern.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.208.193 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=giTGiB+a1M1lvJ0av9Oc5TyDTcpkGYGJthjDlIF5v9E=; b=FHe2WKD668msfopIy4neSUYzwVQiLbkjOptB5YVbXrjrSrd68cD5vDwDblt0GPdy4c S8+2F0V46yEUIwEY30anlRM/M4e7v/ofxmlbpq+jk14J4bXprjEtzajx4L+ha4Hwa2gJ jNtJkTO5gQPCoE77PI/3DjueiBktrT79jCyWh1DZ7IFUqkrm6DOkKn2aIlQ839b1mtyk yU6SL56sPwdK6TdSKN2NFWB8QZwVLDzg/McOg2Rg7YMrXGznil6qEW/VKi3L48Hw3T+B 4ZSD4f/oAJmAJX+Fh13Rw9X5mGtm7hMY1QlG/ZsKHi2OvVYXMvwKZlbudoK0J7aKQC+d F0BA== 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; bh=giTGiB+a1M1lvJ0av9Oc5TyDTcpkGYGJthjDlIF5v9E=; b=MtvCAO64CawSvA9o6cTVWbyUyV02JLjQFeTzScWcE9T9diy/5wSw0AR2XRgsLpInhz MN07ctq7tmOSoVAjmdNRW1f+4TjrDQFBGrrYOGZUEe5SvBfK/qvF5afLTv2JBZFTpYNd wmGM+WwFmlR7uz/7F9Gwkcvhs2ASK/iQ0jAb9/eo8DiLOChJvsk+H0PrUJzIWCSvQRHu 0ea+JzQ1fFocWFSFixWRve3MxXGWqZiOJOrZN0+f3qD8RG/dpJy78LzME64s3xYe4WTT WIgncRjWctX7Uds5Yfpi/VOiaqAzbka7RbS6FxGqIRmm2AWftGcamcC5vYfukFgz8uNl dOzA== X-Gm-Message-State: APjAAAXAxIT4UhcbEqs/qfcSGL963elS7030w4CG4kOCmphFvIPP35OC BC9km62c8W/k1fMB6f6msAxb0rtdcxZSf8E2tMUzmBbM1m4= X-Google-Smtp-Source: APXvYqx1N0bXLwBJ7tQMQUX3+daSBDFfRhj7mViLwzUKGhfgtvvZNqpSiec5NhqKlGW3GXS+guBmUJwMOTMZc28Hw7E= X-Received: by 2002:a05:651c:1109:: with SMTP id d9mr20995682ljo.192.1574673214830; Mon, 25 Nov 2019 01:13:34 -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: Bart Schaefer Date: Mon, 25 Nov 2019 01:13:21 -0800 Message-ID: Subject: Re: [PATCH 2/3] vcs_info/cvs: set vcs_comm[basedir] in VCS_INFO_detect_cvs To: Aleksandr Mezin Cc: Daniel Shahaf , Zsh hackers list Content-Type: multipart/alternative; boundary="0000000000009b91110598282ddd" --0000000000009b91110598282ddd Content-Type: text/plain; charset="UTF-8" On Sun, Nov 24, 2019, 11:32 PM Aleksandr Mezin wrote: > > Also I probably shouldn't have moved the code in the first place. If > the current directory has `CVS/Repository` in it, it means that the > directory is controlled by CVS I have several directories that are BOTH git and CVS repositories, used for keeping two different origins in sync. This is admittedly an unusual situation -- we have a legacy process that expects to fetch sources from CVS, and developers collaborating through git -- but I would be annoyed if vcs didn't find the git data because of the CVS subdir. I would expect the list of repo types in the "enable" style to be handled in the order they appear. --0000000000009b91110598282ddd--