all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mike Kupfer <mkupfer@alum.berkeley.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
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	[thread overview]
Message-ID: <27085.1547770683@alto> (raw)
In-Reply-To: Your message of "Thu, 17 Jan 2019 16:44:26 -0500." <jwvh8e7ezeb.fsf-monnier+gmane.emacs.devel@gnu.org>

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



  reply	other threads:[~2019-01-18  0:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 16:10 Emacs pretest 26.1.91 is out Nicolas Petton
2019-01-07 21:42 ` John Wiegley
2019-01-07 22:11 ` Glenn Morris
2019-01-07 23:03   ` Nicolas Petton
2019-01-08  3:35     ` Eli Zaretskii
2019-01-08  0:59   ` Paul Eggert
2019-01-11  1:03     ` Glenn Morris
2019-01-11  2:31       ` Paul Eggert
2019-01-16 10:30         ` what make-dist should include [was Re: Emacs pretest 26.1.91 is out] Glenn Morris
2019-01-17  5:42           ` Mike Kupfer
2019-01-17 21:44             ` Stefan Monnier
2019-01-18  0:18               ` Mike Kupfer [this message]
2019-01-18  3:01                 ` Stefan Monnier
2019-01-20  1:08                   ` Mike Kupfer
2019-01-20 14:42                     ` Stefan Monnier
2019-01-18  8:38                 ` Eli Zaretskii
2019-01-20  0:54                   ` Mike Kupfer
2019-01-18 18:58             ` Glenn Morris
2019-01-22 21:58           ` Paul Eggert
2019-01-23 16:14             ` Eli Zaretskii
2019-01-23 17:52               ` Paul Eggert
2019-01-23 18:14                 ` Eli Zaretskii
2019-01-08  1:25 ` Emacs pretest 26.1.91 is out Paul Eggert
2019-01-08  8:53   ` Nicolas Petton
2019-01-09 15:02 ` Phillip Lord

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=27085.1547770683@alto \
    --to=mkupfer@alum.berkeley.edu \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.