public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Gejoe Daniel <gejoed@rediffmail.com>
Cc: gcc@gcc.gnu.org, gcc-help@gcc.gnu.org
Subject: Re: [Regarding GCOV].gcda:stamp mismatch with notes file
Date: Thu, 25 Apr 2024 09:57:35 +0100	[thread overview]
Message-ID: <CAH6eHdT5O=PZx3Z9zKs1s7eBgatgorqxWwYA-O_N54QyBh2Rrw@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdT8mBhoLea+3wrJ38==Nq5gcmvdt1LXJfnvrdh5Zqmz0g@mail.gmail.com>

On Thu, 25 Apr 2024 at 09:54, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>
> On Thu, 25 Apr 2024 at 07:47, Gejoe Daniel via Gcc <gcc@gcc.gnu.org> wrote:
> >
> > Hi team,
> > The following is my query posted but would need more inputs :
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114751
> >
> > The gcov tool which was working so far seems to fail with our latest branch where gcc is 11.4.0 and hence we wanted to sort this out by getting the right help as early as possible.
> >
> > Awaiting prompt reply.
> >
> > Thanks to the GCC team for all the help !
>
> Please don't cross-post to both gcc and gcc-help lists. You've already
> reported it to bugzilla, spamming multiple lists isn't needed.

Just to expand on this, either you're discussing development of GCC,
or asking for help using it, but not both. So posting to both lists
isn't usually appropriate.

If it's a "meta topic" like an announcement to all users of GCC
mailing lists then of course sending to multiple lists makes sense.

      reply	other threads:[~2024-04-25  8:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25  6:45 Gejoe Daniel
2024-04-25  7:46 ` Dennis Luehring
2024-04-25  8:54 ` Jonathan Wakely
2024-04-25  8:57   ` Jonathan Wakely [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='CAH6eHdT5O=PZx3Z9zKs1s7eBgatgorqxWwYA-O_N54QyBh2Rrw@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gejoed@rediffmail.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. 
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).