From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: what make-dist should include [was Re: Emacs pretest 26.1.91 is out] Date: Thu, 17 Jan 2019 22:01:43 -0500 Message-ID: References: <27085.1547770683@alto> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1547780395 12623 195.159.176.226 (18 Jan 2019 02:59:55 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 18 Jan 2019 02:59:55 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) Cc: emacs-devel@gnu.org To: Mike Kupfer Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 18 03:59:51 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gkKNq-0003Aj-AX for ged-emacs-devel@m.gmane.org; Fri, 18 Jan 2019 03:59:50 +0100 Original-Received: from localhost ([127.0.0.1]:59154 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gkKPx-00019f-Gh for ged-emacs-devel@m.gmane.org; Thu, 17 Jan 2019 22:02:01 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:54716) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gkKPs-000171-0m for emacs-devel@gnu.org; Thu, 17 Jan 2019 22:01:56 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gkKPo-0000dE-LZ for emacs-devel@gnu.org; Thu, 17 Jan 2019 22:01:53 -0500 Original-Received: from pruche.dit.umontreal.ca ([132.204.246.22]:47371) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gkKPk-0000ZH-6N for emacs-devel@gnu.org; Thu, 17 Jan 2019 22:01:50 -0500 Original-Received: from ceviche.home (lechon.iro.umontreal.ca [132.204.27.242]) by pruche.dit.umontreal.ca (8.14.7/8.14.1) with ESMTP id x0I31huu024461; Thu, 17 Jan 2019 22:01:44 -0500 Original-Received: by ceviche.home (Postfix, from userid 20848) id A5F8166184; Thu, 17 Jan 2019 22:01:43 -0500 (EST) In-Reply-To: <27085.1547770683@alto> (Mike Kupfer's message of "Thu, 17 Jan 2019 16:18:03 -0800") X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 5 X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 2 Rules triggered EDT_SA_DN_PASS=0, RV6463=0 X-NAI-Spam-Version: 2.3.0.9418 : core <6463> : inlines <6997> : streams <1810399> : uri <2781615> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 132.204.246.22 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:232450 Archived-At: > With MQ the workflow is pretty simple: > > 1- unpack the tarball > 2- create the repo and commit the unpacked files > 3- pull the patches from their repo > 4- apply the patches ("hg qpush -a") > 5- build [ The step 0 being "download the tarball". ] Hmm... ignoring the issue of Mercurial -vs- Git, the equivalent using the VCS would be: 0- clone from the remote repository to a local "bare" repository. 1- clone from that local repository 2- do nothing 3- pull the patches from their repo 4- apply the patches 5- build Step 0 is where you'll need/want to convert from the remote VCS format (Git/Mercurial/...) to the one you want to use locally (Mercurial in your case), so that's where the issue of repository format may get in the way (I've used Git to access Mercurial repositories and it works OK, but is significantly slower on large repositories, haven't tried the other direction). Stefan "to me, source code without its VCS repository feels like a computer without connection to the Internet" PS: I should stop here because I'm starting to sound like I'm trying to convince you to change your workflow, whereas I'm only trying to understand your motivation.