From: Stefan Kangas <stefankangas@gmail.com>
To: Andrea Corallo <acorallo@gnu.org>,
Philip Kaludercic <philipk@posteo.net>
Cc: Richard Stallman <rms@gnu.org>, "Alfred M. Szmidt" <ams@gnu.org>,
emacs-devel@gnu.org
Subject: Re: cond* status?
Date: Tue, 18 Jun 2024 12:08:42 -0700 [thread overview]
Message-ID: <CADwFkmne3czzy0in_SC3JahCFviNhOn2=EdTdLrwbUDqFebuZA@mail.gmail.com> (raw)
In-Reply-To: <yp1jzimgjmc.fsf@fencepost.gnu.org>
Andrea Corallo <acorallo@gnu.org> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> Richard Stallman <rms@gnu.org> writes:
>>
>>> [[[ To any NSA and FBI agents reading my email: please consider ]]]
>>> [[[ whether defending the US Constitution against all enemies, ]]]
>>> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>>>
>>> > What is the current status on cond*?
>>>
>>> I am ready to show people a version to try.
>>> I can do by by checking it in, or by posting it on this list.
>>
>> I think the best way to get feedback would be to post it to the list.
>> By checking it in, just before the master branch is going to be cut for
>> the next release might make it difficult to adjust things in the long
>> run.
>
> I agree with Philip would be ideal to have it as a patch (or a dedicated
> git branch).
I think the ship has sailed for getting cond* into Emacs 30 at this
point, but in any case a patch or a branch is better to give people time
to comment before it lands.
next prev parent reply other threads:[~2024-06-18 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 11:38 cond* status? Alfred M. Szmidt
2024-06-17 2:42 ` Richard Stallman
2024-06-17 9:07 ` Philip Kaludercic
2024-06-18 19:02 ` Andrea Corallo
2024-06-18 19:08 ` Stefan Kangas [this message]
2024-06-27 7:43 ` Eli Zaretskii
2024-07-26 11:46 ` Alfred M. Szmidt
2024-07-29 2:38 ` Richard Stallman
2024-07-29 10:16 ` Emanuel Berg
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='CADwFkmne3czzy0in_SC3JahCFviNhOn2=EdTdLrwbUDqFebuZA@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=acorallo@gnu.org \
--cc=ams@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
--cc=rms@gnu.org \
/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).