From: <tomas@tuxteam.de>
To: Psionic K <psionik@positron.solutions>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Where / when Emacs on Gitlab?
Date: Thu, 11 Jan 2024 08:51:11 +0100 [thread overview]
Message-ID: <ZZ+d74csor98Qx0p@tuxteam.de> (raw)
In-Reply-To: <CADQMGASawxgG2YpPV3256R9mF1gz6-2PiLPLwP-DA9bOk7v2qQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
On Thu, Jan 11, 2024 at 03:22:12PM +0900, Psionic K wrote:
> I only just caught Stefan's presentation on Emacs development
> https://toobnix.org/w/m4XmrmE9Geat54AKT1RQaH
[...]
> While these web 2.0 style services have their own drawbacks for
> communication that have become more clear in their 20 years of
> evolution, the better systems are currently under development and we
> should direct attention toward making better things rather than
> applying friction to each other over the drawbacks of these soon-to-be
> ancient web 2.0 platforms [...]
You align things along a "worse...better" line, but let me say
that this valuation corresponds to your opinion, which I do
respect but I don't share at all.
For me, a good mail workflow is way better than any of the Web 2.0
alternatives available (and yes, I do have experience with Gitlab).
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2024-01-11 7:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 6:22 Where / when Emacs on Gitlab? Psionic K
2024-01-11 7:51 ` tomas [this message]
2024-01-11 8:59 ` Uwe Brauer via Emacs development discussions.
2024-01-11 8:52 ` Po Lu
2024-01-11 9:15 ` Eli Zaretskii
2024-01-11 10:42 ` Alan Mackenzie
2024-01-11 10:56 ` Psionic K
2024-01-11 16:40 ` T.V Raman
2024-01-11 22:37 ` Psionic K
2024-01-12 5:01 ` tomas
2024-01-12 5:19 ` Emanuel Berg
2024-01-12 7:21 ` tomas
2024-01-15 2:11 ` Emanuel Berg
2024-01-12 6:49 ` Psionic K
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=ZZ+d74csor98Qx0p@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=emacs-devel@gnu.org \
--cc=psionik@positron.solutions \
/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).