From: Stefan Kangas <stefankangas@gmail.com>
To: "andrés ramírez" <rrandresf@hotmail.com>, "T.V Raman" <raman@google.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Lars Ingebrigtsen <larsi@gnus.org>,
Ulrich Mueller <ulm@gentoo.org>,
Eric Abrahamsen <eric@ericabrahamsen.net>,
emacs-devel@gnu.org
Subject: Re: Can't build previous versions of Emacs?
Date: Fri, 15 Jul 2022 07:50:20 -0700 [thread overview]
Message-ID: <CADwFkmkcCgm5PieAY80JnTVNNkFG==ALEfy9k1Jj2D_K7rC81Q@mail.gmail.com> (raw)
In-Reply-To: <DM6PR03MB38037C379FE0B28A542B4254A68B9@DM6PR03MB3803.namprd03.prod.outlook.com>
andrés ramírez <rrandresf@hotmail.com> writes:
> JIC. If You want to try emacs-20 right now. You try in on netbsd. netbsd
> guys still compile and have a packaged emacs-20.
>
> If You want to try emacs-23. Ulrich and the gentoo guys have a heavily
> patched emacs-23 version still compiling on latest gentoo. And they also
> have an emacs18 still compiling too.
How about installing such patches on the release branches, so that it is
easy to build them on recent machines?
It might even indirectly help with bisecting really old bugs by giving
an idea of which patches might be needed to get various versions to
build.
next prev parent reply other threads:[~2022-07-15 14:50 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmkcCgm5PieAY80JnTVNNkFG==ALEfy9k1Jj2D_K7rC81Q@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=raman@google.com \
--cc=rrandresf@hotmail.com \
--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 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.