From: Greg KH <gregkh@linuxfoundation.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
cfr@inria.fr, cocci@inria.fr, rust-for-linux@vger.kernel.org
Subject: Re: Extending support for mailing list archives?
Date: Tue, 12 Dec 2023 11:21:02 +0100 [thread overview]
Message-ID: <2023121227-shadiness-sagging-6589@gregkh> (raw)
In-Reply-To: <f3e032b9-ee6f-46fc-b686-ce50085bdf3f@web.de>
On Tue, Dec 12, 2023 at 10:25:28AM +0100, Markus Elfring wrote:
> >> How do you think about to support another mailing list archive
> >> on the platform “https://korg.docs.kernel.org/lore.html”?
> >> Or:
> >> Would you like to forward any messages between existing mailing lists?
> >
> > Sorry, I'm not sure what you're asking me. Is this a new list request,
>
> Probably, yes.
>
> https://sympa.inria.fr/sympa/arc/cfr/2023-12/
>
>
> > a request to archive an existing list,
>
> No.
>
>
> > or something else altogether?
>
> I remember your response for the clarification approach “Checking time dimension
> for the migrated message archive” (from 2021-08-25).
> https://lore.kernel.org/cocci/20210825162917.jv6jxmgjbyror6vs@nitro.local/
>
> Thus I imagine that Julia Lawall could trigger the addition of some data
> for such information systems.
>
> See also her constructive response from yesterday.
> https://sympa.inria.fr/sympa/arc/cfr/2023-12/msg00018.html
Hi,
This is the semi-friendly patch-bot of Greg Kroah-Hartman.
Markus, you seem to have sent a nonsensical or otherwise pointless
comment on a Linux kernel developer mailing list. I strongly suggest
that you not do this anymore. Please do not bother developers who are
actively working to produce patches and features with comments that, in
the end, are a waste of time.
Everyone, please ignore Markus's suggestion; you do not need to follow
them at all. The person/bot/AI that sent it is being ignored by almost
all Linux kernel maintainers for having a persistent pattern of behavior
of producing distracting and pointless commentary, and inability to
adapt to feedback. Please feel free to also ignore emails from them.
thanks,
greg k-h's patch email bot
prev parent reply other threads:[~2023-12-12 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 8:36 [cocci] Extending support for mailing list archives? Markus Elfring
2023-12-11 8:36 ` Markus Elfring
2023-12-11 18:08 ` Konstantin Ryabitsev
2023-12-12 9:25 ` [cocci] " Markus Elfring
2023-12-12 9:25 ` Markus Elfring
2023-12-12 10:21 ` Greg KH [this message]
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=2023121227-shadiness-sagging-6589@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Markus.Elfring@web.de \
--cc=cfr@inria.fr \
--cc=cocci@inria.fr \
--cc=konstantin@linuxfoundation.org \
--cc=rust-for-linux@vger.kernel.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.
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.