From: Joel Brobecker <brobecker@adacore.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/2] Add dprintf and detach test (PR breakpoints/17012)
Date: Mon, 07 Jul 2014 20:23:00 -0000 [thread overview]
Message-ID: <20140707202315.GL6038@adacore.com> (raw)
In-Reply-To: <53BAD6DC.2010003@ericsson.com>
> I checked a few other test files and they didn't have the copyright
> notice, that's why I didn't add it. I have no problem adding it if it
> should be there.
Yeah, we've been pretty bad about this in the past, and normally
we should go back and fix all files. But it can be so much work
researching those that we tend to do it piecemeal, when we happen
to notice one of these files. In the meantime, we try to be better
with all new files being added.
--
Joel
prev parent reply other threads:[~2014-07-07 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 14:26 Simon Marchi
2014-06-18 14:26 ` [PATCH 2/2] Only leave dprintf inserted if it is marked as persistent " Simon Marchi
2014-07-02 13:29 ` [PATCH 1/2] Add dprintf and detach test " Simon Marchi
2014-07-07 15:06 ` Joel Brobecker
2014-07-07 17:20 ` Simon Marchi
2014-07-07 20:23 ` Joel Brobecker [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=20140707202315.GL6038@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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