all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>, Po Lu <luangruo@yahoo.com>
Cc: "T.V Raman" <raman@google.com>,
	"João Távora" <joaotavora@gmail.com>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: Permanently fix org versioning breakage during builds?
Date: Sun, 24 Dec 2023 06:11:37 -0800	[thread overview]
Message-ID: <CADwFkm=wmcORLOpntNpMRTNJbKbq=c3MyF3uiYjwXajdB9TpRw@mail.gmail.com> (raw)
In-Reply-To: <87plyv7oii.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

> Po Lu <luangruo@yahoo.com> writes:
>
>> What do you say to disabling the mechanism for version checks in Org as
>> distributed with Emacs?  Nothing will be lost, since AFAIU the check
>> exists for the sake of conflicting Org installations set in place by
>> package managers rather than Emacs itself.
>
> Considering the existing stance that it is ok to break things
> occasionally due to stale macros when running make on Emacs git
> repository, I see no problem disabling these checks for built-in Org
> mode.
>
> Tentatively, it may even be done without affecting version check for
> out-of-tree builds. See the attached patch.

Could you explain the benefit of doing that?  Is the problem simply that
some users building from emacs.git don't want to say "make bootstrap",
or is it something else?

What will be the consequences for everyone else, if we were to install
the proposed change?



  parent reply	other threads:[~2023-12-24 14:11 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22 17:27 Permanently fix org versioning breakage during builds? T.V Raman
2023-12-23 17:58 ` João Távora
2023-12-23 18:06   ` Ihor Radchenko
2023-12-23 18:44     ` João Távora
2023-12-24 11:50       ` Ihor Radchenko
2023-12-24 14:13         ` João Távora
2023-12-24 14:48           ` Ihor Radchenko
2023-12-24 16:32             ` João Távora
2023-12-24 16:36               ` T.V Raman
2023-12-24 17:00                 ` Eli Zaretskii
2023-12-24 17:04               ` João Távora
2023-12-24 17:16                 ` Ihor Radchenko
2023-12-24 17:48                   ` João Távora
2023-12-24 18:13                     ` T.V Raman
2023-12-24 18:52                       ` Eli Zaretskii
2023-12-24 18:13                     ` Ihor Radchenko
2023-12-24 23:11                       ` João Távora
2023-12-25 11:26                         ` &allow-other-keys + &rest body in cl-defmacro (was: Permanently fix org versioning breakage during builds?) Ihor Radchenko
2023-12-25 12:09                           ` João Távora
2023-12-25 12:21                             ` Ihor Radchenko
2023-12-25 19:00                           ` Ihor Radchenko
2023-12-25 13:58                         ` Permanently fix org versioning breakage during builds? Ihor Radchenko
2023-12-25 17:42                           ` João Távora
2023-12-25 18:24                             ` Ihor Radchenko
2023-12-24 17:05               ` Ihor Radchenko
2023-12-24 17:12                 ` João Távora
2023-12-24 17:18                   ` Ihor Radchenko
2023-12-24 17:24                     ` Ihor Radchenko
2023-12-24 17:54                       ` João Távora
2023-12-24 18:10                         ` Ihor Radchenko
2023-12-24 18:16                           ` João Távora
2023-12-24 18:23                             ` Ihor Radchenko
2023-12-24 18:47                           ` Eli Zaretskii
2023-12-24 18:56                             ` Ihor Radchenko
2023-12-24 18:57                               ` Eli Zaretskii
2023-12-24 18:42                         ` Eli Zaretskii
2023-12-24 14:56           ` Eli Zaretskii
2023-12-24 23:14             ` João Távora
2023-12-24  2:43     ` T.V Raman
2023-12-24  6:51       ` Eli Zaretskii
2023-12-24 16:29         ` T.V Raman
2023-12-24 16:56           ` Eli Zaretskii
2023-12-24 11:00       ` Ihor Radchenko
2023-12-24 12:32         ` Po Lu
2023-12-24 12:50           ` Ihor Radchenko
2023-12-24 12:57             ` Po Lu
2023-12-24 14:11             ` Stefan Kangas [this message]
2023-12-24 14:51               ` Ihor Radchenko
2023-12-24 14:58                 ` Eli Zaretskii
2023-12-24 16:59                   ` Ihor Radchenko
2023-12-24 17:26                     ` T.V Raman
2023-12-24 17:44                       ` Ihor Radchenko
2023-12-24 18:01                         ` João Távora
2023-12-24 18:12                           ` Ihor Radchenko
2023-12-24 18:16                             ` T.V Raman
2023-12-24 18:25                               ` Ihor Radchenko
2023-12-24 18:53                               ` Eli Zaretskii
2023-12-24 18:48                             ` Eli Zaretskii
2023-12-24 19:23                               ` Stefan Kangas
2023-12-24 18:45                           ` Eli Zaretskii
2023-12-24 18:11                         ` T.V Raman
2023-12-24 18:17                           ` Ihor Radchenko
2023-12-24 19:31                             ` T.V Raman
2023-12-24 18:51                           ` Eli Zaretskii
2023-12-24 17:56                       ` João Távora
2023-12-24 18:36                       ` Eli Zaretskii
2023-12-24 18:32                     ` Eli Zaretskii
2023-12-24 18:50                       ` Ihor Radchenko
2023-12-24 18:55                         ` Eli Zaretskii
2023-12-24 19:05                           ` Ihor Radchenko
2023-12-24 23:23                       ` João Távora
2023-12-24 19:16                     ` Stefan Kangas
2023-12-24 19:24                       ` Ihor Radchenko
2023-12-24 16:32               ` T.V Raman
2023-12-24 16:39                 ` João Távora
2023-12-24 16:58                   ` Eli Zaretskii
2023-12-24 17:05                     ` João Távora
2023-12-24 18:34                       ` Eli Zaretskii
2023-12-25 18:59             ` Ihor Radchenko
2023-12-25 19:27               ` Eli Zaretskii
2023-12-25 20:02                 ` Ihor Radchenko
2023-12-25 20:03                   ` Eli Zaretskii

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='CADwFkm=wmcORLOpntNpMRTNJbKbq=c3MyF3uiYjwXajdB9TpRw@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=luangruo@yahoo.com \
    --cc=raman@google.com \
    --cc=yantar92@posteo.net \
    /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.