unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Ulrich Mueller <ulm@gentoo.org>,
	 Eric Abrahamsen <eric@ericabrahamsen.net>,
	 emacs-devel@gnu.org
Subject: Re: Can't build previous versions of Emacs?
Date: Thu, 14 Jul 2022 20:41:13 +0200	[thread overview]
Message-ID: <87y1wvo7ue.fsf@gnus.org> (raw)
In-Reply-To: <jwv4jzjfspe.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 14 Jul 2022 14:38:34 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> In my case, I never (or at least very rarely) care about building
> exactly the actual release and I prefer building from the
> `emacs-NN` branch.
>
> Typically the main purpose is to run some older Emacs to see if some
> ELisp code works on that older version and the difference between
> `emacs-NN` and the actual release is negligible in that case.

I don't oppose checking in that fix on all the -NN branches, but I do
care about building the exact versions a lot (when doing bug triage).

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2022-07-14 18:41 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14  3:23 Can't build previous versions of Emacs? Eric Abrahamsen
2022-07-14  3:33 ` Po Lu
2022-07-14 16:13   ` Eric Abrahamsen
2022-07-14 17:07     ` Ulrich Mueller
2022-07-14 17:24       ` Lars Ingebrigtsen
2022-07-14 18:21         ` Stefan Monnier
2022-07-14 18:23           ` Lars Ingebrigtsen
2022-07-14 18:38             ` Stefan Monnier
2022-07-14 18:41               ` Lars Ingebrigtsen [this message]
2022-07-14 19:33                 ` Andreas Schwab
2022-07-14 21:52                 ` Stefan Kangas
2022-07-15  9:47                   ` Lars Ingebrigtsen
2022-07-15 13:37                     ` Stefan Kangas
2022-07-16 10:31                       ` Lars Ingebrigtsen
2022-07-16 11:03                         ` Po Lu
2022-07-16 11:05                           ` Lars Ingebrigtsen
2022-07-16 11:17                           ` Ulrich Mueller
2022-07-16 12:49                             ` Po Lu
2022-07-16 13:01                               ` Lars Ingebrigtsen
2022-07-16 14:54                                 ` Ulrich Mueller
2022-07-16 16:10                                   ` Lars Ingebrigtsen
2022-07-14 23:30           ` T.V Raman
2022-07-15 14:03             ` andrés ramírez
2022-07-15 14:50               ` Stefan Kangas
2022-07-15 15:30                 ` Eli Zaretskii
2022-07-16 20:59             ` Karl Berry
2022-07-17  0:49               ` Po Lu
2022-07-17  5:35                 ` Eli Zaretskii
2022-07-17  8:04                   ` Gregory Heytings
2022-07-17  8:53                     ` Po Lu
2022-07-17  8:56                       ` Gregory Heytings
2022-07-17  9:27                         ` Po Lu
     [not found]                   ` <DM6PR03MB3803454A10E226097F5A3877A68D9@DM6PR03MB3803.namprd03.prod.outlook.com>
     [not found]                     ` <83wncbq2ya.fsf@gnu.org>
2022-07-17 15:44                       ` andrés ramírez
2022-07-14 19:02       ` Alan Mackenzie
2022-07-14 17:01   ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87y1wvo7ue.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=monnier@iro.umontreal.ca \
    --cc=ulm@gentoo.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).