all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Stefan Kangas <stefan@marxist.se>
Cc: 50985@debbugs.gnu.org
Subject: bug#50985: Merging gnulib for Emacs 28.1?
Date: Sun, 3 Oct 2021 12:37:38 -0700	[thread overview]
Message-ID: <c5867a88-4ad4-6ddc-2105-8173fe9447e6@cs.ucla.edu> (raw)
In-Reply-To: <CADwFkm=KzVJdvez4Kv_03bhv9ipbs-m7TVpNNwbQ0aJ9J9KgwA@mail.gmail.com>

On 10/2/21 8:42 PM, Stefan Kangas wrote:
> Should we merge the latest changes from Gnulib into the emacs-28
> branch?

Yes, as there have been a fair number of Gnulib changes that Emacs could 
use for the usual portability and correctness reasons. Among other 
things, emacs-28 currently doesn't build on Fedora 34 (the current 
Fedora release) when you configure with --enable-gcc-warnings.

In July Eli gave the OK for me to merge Gnulib (see Bug#33847) but 
unfortunately I put it off. I'll look into doing that now.





  reply	other threads:[~2021-10-03 19:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-03  3:42 bug#50985: Merging gnulib for Emacs 28.1? Stefan Kangas
2021-10-03 19:37 ` Paul Eggert [this message]
2021-10-04  6:37   ` Paul Eggert
2021-10-04 12:19     ` Eli Zaretskii
2021-10-04 22:26       ` Paul Eggert
2021-10-04 23:18       ` Andy Moreton
2021-10-04 23:44         ` Andy Moreton
2021-10-05 12:44           ` Ken Brown
2021-10-05 12:59           ` Eli Zaretskii
2021-10-05 12:58         ` Eli Zaretskii
2021-10-05 13:44           ` Robert Pluim
2021-10-05 14:09             ` Ken Brown
2021-10-05 14:11               ` Robert Pluim
2021-10-05 16:16                 ` Paul Eggert
2021-10-05 18:15                   ` Andy Moreton
2021-10-06  7:23                   ` Robert Pluim
2021-10-05 16:19               ` Paul Eggert
2021-10-07  9:14 ` 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=c5867a88-4ad4-6ddc-2105-8173fe9447e6@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=50985@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    /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.