From: Theodor Thornhill <theo@thornhill.no>
To: Po Lu <luangruo@yahoo.com>
Cc: Stefan Kangas <stefankangas@gmail.com>,
Vitaly Ankh <vitalyankh@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Please stop this
Date: Wed, 22 Dec 2021 08:05:35 +0100 [thread overview]
Message-ID: <8AFBAEFD-9A6D-407F-BDF6-41215E6101C5@thornhill.no> (raw)
In-Reply-To: <87o859qg80.fsf@yahoo.com>
On 22 December 2021 07:57:35 CET, Po Lu <luangruo@yahoo.com> wrote:
>Theodor Thornhill <theo@thornhill.no> writes:
>
>> On 22 December 2021 06:30:30 CET, Po Lu <luangruo@yahoo.com> wrote:
>
>> Well, apologies if you feel I waste your time. I have no interest in
>> participating in such a "flame fest", as I feel I have not done
>> before.
>
>No, I didn't mean that you were wasting time -- I meant to say that the
>topic itself tends to result in long and repetitive threads that never
>seem to get anything done, so IMHO it's not worth bringing up at this
>point.
I agree, that is why I started this thread by concretely proposing to assemble a list, or at least reaching some tactile result quickly.
Now there at least is a dedicated user for emacs over at srht. I'll look into converting some issues from debbugs as well. Then most of the workflow is represented. I invite you to take a look.
Thanks
next prev parent reply other threads:[~2021-12-22 7:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 20:32 Migrating to sourcehut - what's missing? Vitaly Ankh
2021-12-21 21:09 ` Stefan Kangas
2021-12-22 1:02 ` Please stop this (was: Re: Migrating to sourcehut - what's missing?) Po Lu
2021-12-22 1:34 ` Please stop this Po Lu
2021-12-22 5:07 ` Please stop this (was: Re: Migrating to sourcehut - what's missing?) Stefan Kangas
2021-12-22 5:30 ` Please stop this Po Lu
2021-12-22 6:36 ` Theodor Thornhill
2021-12-22 6:57 ` Po Lu
2021-12-22 7:05 ` Theodor Thornhill [this message]
2021-12-22 4:16 ` Migrating to sourcehut - what's missing? Richard Stallman
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=8AFBAEFD-9A6D-407F-BDF6-41215E6101C5@thornhill.no \
--to=theo@thornhill.no \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=stefankangas@gmail.com \
--cc=vitalyankh@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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.