From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: indieterminacy <indieterminacy@libre.brussels>
Cc: Andrew Tropin <andrew@trop.in>,
csantosb@inventati.org, Simon Tournier <zimon.toutoune@gmail.com>,
John Kehayias <john.kehayias@protonmail.com>,
guix-devel@gnu.org
Subject: Re: Emacs next variants
Date: Sun, 12 Mar 2023 13:51:20 +0100 [thread overview]
Message-ID: <23be50059c7ad8ef8f712357e1578eb3569a65ca.camel@gmail.com> (raw)
In-Reply-To: <37c98f7a88b22cab26d3d15a16dcbfd6@libre.brussels>
Am Sonntag, dem 12.03.2023 um 10:46 +0100 schrieb indieterminacy:
> Out of curiosity, where do such prescriptions concerning one tool or
> a set of tools get documented?
It isn't, but note the manual on version numbers leads with
> We usually package only the latest version of a given free software
> project. But sometimes, for instance for incompatible library
> versions, two (or more) versions of the same package are needed.
emacs is a notable exception here due to emacs next almost always
existing.
Cheers
next prev parent reply other threads:[~2023-03-12 12:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 18:51 Emacs next variants Cayetano Santos
2023-03-10 12:07 ` Simon Tournier
2023-03-10 14:56 ` Cayetano Santos
2023-03-10 15:39 ` Simon Tournier
2023-03-10 16:59 ` John Kehayias
2023-03-10 18:14 ` Simon Tournier
2023-03-10 18:24 ` Cayetano Santos
2023-03-10 18:44 ` Andrew Tropin
2023-03-10 19:36 ` Liliana Marie Prikler
2023-03-12 5:18 ` Andrew Tropin
2023-03-12 7:46 ` Liliana Marie Prikler
2023-03-12 8:47 ` Andrew Tropin
2023-04-26 18:52 ` Mekeor Melire
2023-06-13 5:26 ` Andrew Tropin
2023-03-12 9:46 ` indieterminacy
2023-03-12 12:51 ` Liliana Marie Prikler [this message]
2023-03-10 20:39 ` Cayetano Santos
2023-03-12 5:11 ` Andrew Tropin
2023-03-10 18:36 ` Andrew Tropin
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=23be50059c7ad8ef8f712357e1578eb3569a65ca.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=andrew@trop.in \
--cc=csantosb@inventati.org \
--cc=guix-devel@gnu.org \
--cc=indieterminacy@libre.brussels \
--cc=john.kehayias@protonmail.com \
--cc=zimon.toutoune@gmail.com \
/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/guix.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.