From: Mark Wielaard <mark@klomp.org>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: valgrind-developers@lists.sourceforge.net,
Martin Cermak <mcermak@redhat.com>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] valgrind-announce: Update valgrind ML
Date: Fri, 16 May 2025 11:31:29 +0200 [thread overview]
Message-ID: <20250516093129.GG12775@gnu.wildebeest.org> (raw)
In-Reply-To: <aCb7Pi6Vgkc8OMja@yuki.lan>
Hi,
On Fri, May 16, 2025 at 10:45:50AM +0200, Cyril Hrubis wrote:
> > valgrind-developers has heavy traffic, use valgrind-announce.
>
> Was this requested by valgrind devs? I suppose this is fine as long as
> we get their ack.
I think valgrind-developers is a better place for announcing new
versions of LTP. We can then update our own valgrind testing.
valgrind-announce is really for users when valgrind itself has a new
release.
Cheers,
Mark
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-05-16 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 7:51 [LTP] [PATCH] valgrind-announce: Update valgrind ML Petr Vorel
2025-05-16 8:45 ` Cyril Hrubis
2025-05-16 9:31 ` Mark Wielaard [this message]
2025-05-16 12:09 ` Petr Vorel
2025-05-16 12:12 ` Mark Wielaard
2025-05-16 12:22 ` Petr Vorel
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=20250516093129.GG12775@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mcermak@redhat.com \
--cc=valgrind-developers@lists.sourceforge.net \
/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.