From: Ihor Radchenko <firstname.lastname@example.org>
To: email@example.com, Bastien <firstname.lastname@example.org>
Cc: Emacs orgmode <email@example.com>
Subject: Re: [BUG] Emacs-29.0.60: (setopt org-babel-load-languages ...) may cause warnings
Date: Thu, 02 Feb 2023 08:26:56 +0000 [thread overview]
Message-ID: <87pmasqxpr.fsf@localhost> (raw)
>> May you please convert the diff into a patch with changelog entry and
>> commit message? See
> patch attached.
> 1. I have assigned my copyright for Emacs stuff to the FSF
Bastien, may you please confirm?
> 2. My initial version of the patch was against bugfix and now I have set
> :package-version to "9.6"
You can also remove :version tag while we are at it. It is redundant
when :package-version is provided (we are slowly getting rid of the
:version tags across Org).
> according to the instructions on the org-contribute page. I do not
> know if this is acceptable (it
> feels a bit like breaking the rules), but I am happy to redo the
> patch for main.
bugfix is fine. This is a trivial patch.
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-02-02 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 7:19 [BUG] Emacs-29.0.60: (setopt org-babel-load-languages ...) may cause warnings gerard.vermeulen
2023-01-31 10:34 ` Ihor Radchenko
2023-02-01 14:22 ` gerard.vermeulen
2023-02-02 8:26 ` Ihor Radchenko [this message]
2023-02-02 19:33 ` gerard.vermeulen
2023-03-03 14:58 ` Ihor Radchenko
2023-02-28 9:31 ` Bastien Guerry
2023-03-03 15:00 ` Ihor Radchenko
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).