From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Mike Kupfer 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 16:18:03 -0800 Message-ID: <27085.1547770683@alto> References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: blaine.gmane.org 1547770612 11871 195.159.176.226 (18 Jan 2019 00:16:52 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 18 Jan 2019 00:16:52 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 18 01:16:48 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 1gkHq4-0002yu-5Z for ged-emacs-devel@m.gmane.org; Fri, 18 Jan 2019 01:16:48 +0100 Original-Received: from localhost ([127.0.0.1]:57855 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gkHsA-0008Bl-0C for ged-emacs-devel@m.gmane.org; Thu, 17 Jan 2019 19:18:58 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:51494) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gkHrQ-0008Bd-Kf for emacs-devel@gnu.org; Thu, 17 Jan 2019 19:18:13 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gkHrQ-0002ni-07 for emacs-devel@gnu.org; Thu, 17 Jan 2019 19:18:12 -0500 Original-Received: from shell1.rawbw.com ([198.144.192.42]:22365) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gkHrP-0002n3-OW for emacs-devel@gnu.org; Thu, 17 Jan 2019 19:18:11 -0500 Original-Received: from alto (96-95-200-133-static.hfc.comcastbusiness.net [96.95.200.133]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id x0I0I3jH099598 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Jan 2019 16:18:09 -0800 (PST) (envelope-from mkupfer@alum.berkeley.edu) X-Authentication-Warning: shell1.rawbw.com: Host 96-95-200-133-static.hfc.comcastbusiness.net [96.95.200.133] claimed to be alto In-Reply-To: Your message of "Thu, 17 Jan 2019 16:44:26 -0500." X-Mailer: MH-E 8.6+git; nmh 1.6; GNU Emacs 26.1.90 Content-ID: <27084.1547770683.1@alto> X-detected-operating-system: by eggs.gnu.org: FreeBSD 9.x X-Received-From: 198.144.192.42 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:232445 Archived-At: Stefan Monnier wrote: > > When I unpack an Emacs tarball, I usually check it into a fresh > > Mercurial repo before building. > > Interesting. I wonder why you do that. It's so I can apply in-progress patches using Mercurial Queues (MQ). > To me, if I wanted to have a backing VCS, I'd start from a `git clone` > rather than a tarball. Maybe there's an easy way to manage this with Git, but I don't see one. First, I want to build, with the patches, on multiple systems. That means rebasing is out, or at least it becomes more of a hassle. Second, the patches are usually independent. So, IIUC, the "correct" approach would be to have a branch for each patch, plus another branch to merge all the per-patch branches, so that I can build with them all. With MQ the workflow is pretty simple: - unpack the tarball - create the repo and commit the unpacked files - pull the patches from their repo - apply the patches ("hg qpush -a") - build mike