unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Theodor Thornhill <theo@thornhill.no>
To: Po Lu <luangruo@yahoo.com>, Stefan Kangas <stefankangas@gmail.com>
Cc: Vitaly Ankh <vitalyankh@gmail.com>, emacs-devel@gnu.org
Subject: Re: Please stop this
Date: Wed, 22 Dec 2021 07:36:16 +0100	[thread overview]
Message-ID: <EA9B6CB7-E13D-4A13-9A9D-19DB456EA499@thornhill.no> (raw)
In-Reply-To: <8735mlrytl.fsf@yahoo.com>



On 22 December 2021 06:30:30 CET, Po Lu <luangruo@yahoo.com> wrote:
>Stefan Kangas <stefankangas@gmail.com> writes:
>
>> That will not happen, as I'm sure you must understand.  It would be
>> completely counter-productive, and only serve to harm and obstruct
>> important ongoing work.
>>
>> Moreover, I don't understand how Emacs would ever be successful if the
>> reply to volunteers coming here hoping to help should be "we discussed
>> this N months ago, go away".  Luckily, our policy is not that, but to
>> encourage and help them contribute in the most useful way.
>
>AFAICS, discussions about this topic tend to turn into a big runaway
>flamefest, usually starting from simple questions such as "what's
>missing".  This happens every single time someone posts something like
>this and the amount of information gets repeated is frightening, so I
>hope these discussions will crop up less often than every two or so
>months.  Not that I'm opposed to healthy discussion, but the usual
>result of this topic is not that.
>
>Just my two cents though, so feel free to disregard that.
>
>> Yes, something very significant has changed.  Two people have now agreed
>> to start working on this.
>
>Good to hear.
>
>> If you don't want to see this topic may I recommend using an email
>> client that allows you to filter threads you are not interested in?
>
>I already have such topics split to a separate group in Gnus, but
>unfortunately the subject line regexp didn't match on "SourceHut", like
>last time when it only matched on "migrate" and not "migration".
>
>Thanks.

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. 

Theo 



  reply	other threads:[~2021-12-22  6:36 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 [this message]
2021-12-22  6:57           ` Po Lu
2021-12-22  7:05             ` Theodor Thornhill
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

  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=EA9B6CB7-E13D-4A13-9A9D-19DB456EA499@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 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).