From: Michael Elizabeth Chastain <mec@shout.net>
To: ezannoni@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC/WIP] unit test for separate debug info
Date: Fri, 07 Nov 2003 20:21:00 -0000 [thread overview]
Message-ID: <200311072021.hA7KLeCY024925@duracef.shout.net> (raw)
> (BTW, should cloned files retain the original copyright years?)
I believe so.
> Anyway, this needs some pounding by Michael, I think. There probably
> are improvements/changes that could be made.
Okay, I'll jump on it!
Michael C
next reply other threads:[~2003-11-07 20:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 20:21 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-11 21:19 Michael Elizabeth Chastain
2003-11-11 21:22 ` Daniel Jacobowitz
2003-11-12 14:44 ` Elena Zannoni
2003-11-08 1:28 Michael Elizabeth Chastain
2003-11-11 16:26 ` Elena Zannoni
2003-11-07 20:03 Elena Zannoni
2003-11-07 20:39 ` Kevin Buettner
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=200311072021.hA7KLeCY024925@duracef.shout.net \
--to=mec@shout.net \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.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