From: Michael Albinus <michael.albinus@gmx.de>
To: Kyle Meyer <kyle@kyleam.com>
Cc: Stefan Kangas <stefan@marxist.se>, emacs-devel@gnu.org
Subject: Org tests in Emacs (was: emacs-28 b8b2dd1: Update to Org 9.5.1-11-g96d91b)
Date: Tue, 30 Nov 2021 09:31:59 +0100 [thread overview]
Message-ID: <87o8629h8g.fsf_-_@gmx.de> (raw)
In-Reply-To: <87o862dyyb.fsf@kyleam.com> (Kyle Meyer's message of "Mon, 29 Nov 2021 23:55:40 -0500")
Kyle Meyer <kyle@kyleam.com> writes:
Hy Kyle,
>> Btw, Org's test suite is huge IIRC. Would it make sense to merge this
>> also to Emacs? At least the CI/CD test runs on hydra and emba could use
>> them, I believe.
>
> Yes, I think that makes sense, though I probably won't have time to look
> into it very soon. Aside from potential code adjustments that may be
> necessary, I suppose copyright assignments need to be checked. Most of
> the test files list individuals as copyright holders. At a glance, I'm
> not confident that all the authors have paperwork on file.
I see. Maybe we could start iteratively? That means, adapt the test
files where's no copyright problem, and bring them to Emacs git. For the
other files, we will contact the authors, and bring them to Emacs case
by case, when the copyright has been fixed.
If needed, I could help you. Just tell me.
Btw, you could runn all tests under test/lisp/org by
make -C test check-lisp-org
And the dust on emba.gnu.org settled. That is, whenever there is a
change in either lisp/org/*.el or test/lisp/org/*.el, all tests under
test/lisp/org/*.el will run automatically, as regression test. An extra
bonus, isn't it?
See <https://emba.gnu.org/emacs/emacs/-/pipelines>
Best regards, Michael.
next prev parent reply other threads:[~2021-11-30 8:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211127213324.10400.95314@vcs0.savannah.gnu.org>
[not found] ` <20211127213326.7715520D11@vcs0.savannah.gnu.org>
2021-11-28 15:15 ` emacs-28 b8b2dd1: Update to Org 9.5.1-11-g96d91b Michael Albinus
2021-11-28 15:44 ` Kyle Meyer
2021-11-28 16:02 ` Michael Albinus
2021-11-30 4:55 ` Kyle Meyer
2021-11-30 8:31 ` Michael Albinus [this message]
2021-11-30 9:03 ` Current status of emba.gnu.org? Stefan Kangas
2021-11-30 14:38 ` Michael Albinus
2021-11-30 15:44 ` Stefan Kangas
2021-11-30 16:41 ` Michael Albinus
2021-11-30 21:38 ` Stefan Monnier
2021-12-01 9:09 ` Michael Albinus
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=87o8629h8g.fsf_-_@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=kyle@kyleam.com \
--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 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).