From: Daniel Jacobowitz <drow@mvista.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: Elena Zannoni <ezannoni@redhat.com>,
"Gdb-Patches@Sources.Redhat.Com" <gdb-patches@sources.redhat.com>
Subject: Re: [patch] testcases for PRs 1291 and 1431
Date: Mon, 03 Nov 2003 17:41:00 -0000 [thread overview]
Message-ID: <20031103174137.GA29893@nevyn.them.org> (raw)
In-Reply-To: <047701c3a230$68856b50$0202040a@catdog>
On Mon, Nov 03, 2003 at 12:32:09PM -0500, Kris Warkentin wrote:
> > Kris Warkentin writes:
> > > In the end I split them up like so. The 1291 testcase now only
> exhibits the
> > > one issue and the 1431 kfails the second.
> > >
> >
> > Yes, just one thing, can you add a copyright notice to the .c files?
>
> Elena, I don't see copyrights on any of the other c files in the testsuite.
Yes - this is a thing we've been lax about in the past and are trying
to correct.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-11-03 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 18:02 Kris Warkentin
2003-11-02 20:39 ` Elena Zannoni
2003-11-03 17:31 ` Kris Warkentin
2003-11-03 17:41 ` Daniel Jacobowitz [this message]
2003-11-03 18:03 ` Kris Warkentin
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=20031103174137.GA29893@nevyn.them.org \
--to=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kewarken@qnx.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