From: Tim Cross <email@example.com>
Subject: Re: [BUG] Info JS does not work [9.5.3 (release_9.5.3-467-g2bd34e @ /Users/salutis/src/org-mode/lisp/)]
Date: Thu, 22 Sep 2022 06:23:31 +1000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Ihor Radchenko <email@example.com> writes:
> Bastien <firstname.lastname@example.org> writes:
>>> Also, having an actual mirror in sr.ht means that we may set up automatic
>>> tests. WDYT about this idea?
>> Tests are useful if they prevent contributors from changing the code
>> in a way that break them: this must happen before pushing changes to
>> the bugfix or main branches.
>> Automated tests are useful only if we fail to enforce this policy...
>> so I'm not in favor of them.
> I agree that running tests is a good idea before pushing changes.
> However, it is a big ask for contributors when we need to ensure
> compatibility with multiple Emacs versions. Running tests on all the
> supported Emacs version simply takes too much time. Not to mention that
> installing multiple Emacs versions may not be trivial. Automated tests
> could cater backwards compatibility checks.
+1 on this. However, I do wonder if different positions are due to
different understanding of what we mean when talking about automated
next prev parent reply other threads:[~2022-09-21 20:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 9:12 [BUG] Info JS does not work [9.5.3 (release_9.5.3-467-g2bd34e @ /Users/salutis/src/org-mode/lisp/)] Rudolf Adamkovič
2022-05-02 10:08 ` Ihor Radchenko
2022-05-29 10:08 ` Bastien
2022-05-30 3:29 ` Ihor Radchenko
2022-05-31 6:51 ` Bastien
2022-06-12 11:50 ` Bastien
2022-06-14 4:20 ` Ihor Radchenko
2022-06-14 7:20 ` Bastien
2022-06-21 14:26 ` Ihor Radchenko
2022-06-22 3:41 ` Bastien
2022-06-22 4:11 ` Ihor Radchenko
2022-09-18 8:13 ` Bastien
2022-09-20 8:31 ` Ihor Radchenko
2022-09-20 9:01 ` Bastien
2022-09-20 9:26 ` Ihor Radchenko
2022-09-21 20:23 ` Tim Cross [this message]
2022-09-22 15:32 ` Bastien
2022-10-01 12:24 ` Bastien Guerry
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).