From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC] Send new ARI warnings to gdb_testers mailing list
Date: Wed, 06 May 2009 16:46:00 -0000 [thread overview]
Message-ID: <001d01c9ce6a$1d6d7e20$58487a60$@u-strasbg.fr> (raw)
In-Reply-To: <20090506163051.GL10734@adacore.com>
I just committed this with my email address
and will inform you of the first results I get.
Pierre
> -----Message d'origine-----
> De : Joel Brobecker [mailto:brobecker@adacore.com]
> Envoyé : Wednesday, May 06, 2009 6:31 PM
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org
> Objet : Re: [RFC] Send new ARI warnings to gdb_testers mailing list
>
> > The only drawback is that the line number also does not appear
> > on the generated email...
>
> Initially, I thought that this was a pretty significant drawback.
> But I tried to come up with a way of isolating the new line, and
> I'm not sure whether this is possible or not. The problem is that
> the line number associated to an error/warning can change from
> day to day, as we modify the source around it.
>
> We could try your current approach, and see if that helps or not...
> Why not activating your change, but with yourself as the the only
> recipient, as opposed to gdb-testers? That will allow you to determine
> the frequency of such messages, as we as how difficult it is to
> determine which entry is the new one...
>
> --
> Joel
next prev parent reply other threads:[~2009-05-06 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 22:10 Pierre Muller
2009-04-23 18:42 ` Joel Brobecker
2009-05-01 9:24 ` Pierre Muller
2009-05-06 16:31 ` Joel Brobecker
2009-05-06 16:46 ` Pierre Muller [this message]
2009-05-19 8:35 ` Pierre Muller
2009-05-20 5:23 ` Joel Brobecker
2009-10-08 11:15 ` Pierre Muller
2009-10-08 15:52 ` Joel Brobecker
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='001d01c9ce6a$1d6d7e20$58487a60$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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