From: "Frank Ch. Eigler" <fche@redhat.com>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: Aaron Merey <amerey@redhat.com>, elfutils-devel@sourceware.org
Subject: Re: [PATCH] Fix 'make coverage' when used with lcov version 2.0+
Date: Thu, 9 May 2024 18:08:05 -0400 [thread overview]
Message-ID: <20240509220805.GK19769@redhat.com> (raw)
In-Reply-To: <20240509215339.GA16854@altlinux.org>
Hi -
On Fri, May 10, 2024 at 12:53:39AM +0300, Dmitry V. Levin wrote:
> > Pushed as commit ca8ad4648197
>
> What's the purpose of sending proposed patches to the mailing list
> if reviews are silently ignored?
Please be collegial and don't exaggerate.
- FChE
next prev parent reply other threads:[~2024-05-09 22:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 20:45 Aaron Merey
2024-05-06 23:35 ` Dmitry V. Levin
2024-05-08 16:28 ` Aaron Merey
2024-05-09 21:53 ` Dmitry V. Levin
2024-05-09 22:08 ` Frank Ch. Eigler [this message]
2024-05-09 22:59 ` Dmitry V. Levin
2024-05-09 23:03 ` Frank Ch. Eigler
2024-05-10 0:16 ` Dmitry V. Levin
2024-05-10 1:37 ` Frank Ch. Eigler
2024-05-14 15:39 ` Mark Wielaard
2024-05-09 23:24 ` [COMMITTED] Makefile.am: Avoid code duplication Aaron Merey
2024-05-09 23:36 ` Dmitry V. Levin
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=20240509220805.GK19769@redhat.com \
--to=fche@redhat.com \
--cc=amerey@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=ldv@altlinux.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 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).