From: Jim Blandy <jimb@codesourcery.com>
To: Pedro Alves <pedro_alves@portugalmail.pt>
Cc: Vladimir Prus <vladimir@codesourcery.com>,
gdb-patches@sources.redhat.com
Subject: Re: [9/9] expand locations
Date: Sat, 08 Sep 2007 01:41:00 -0000 [thread overview]
Message-ID: <m3ps0url0j.fsf@codesourcery.com> (raw)
In-Reply-To: <46E1EAE8.7070603@portugalmail.pt> (Pedro Alves's message of "Sat, 08 Sep 2007 01:20:56 +0100")
Pedro Alves <pedro_alves@portugalmail.pt> writes:
> Just one boring question from the newbie:
>
> Is the the below the correct thing to do put in the headers of the
> new .exp files? Not just the GPL2, but also the dates, and the
> credit (, and the bug mailing list)?
Ah, thanks. All that does need to be updated to match the rest of
GDB.
next prev parent reply other threads:[~2007-09-08 1:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 23:14 Vladimir Prus
2007-09-08 0:21 ` Pedro Alves
2007-09-08 1:41 ` Jim Blandy [this message]
2007-09-08 3:42 ` Daniel Jacobowitz
2007-09-08 11:50 ` Eli Zaretskii
2007-09-23 8:22 ` Vladimir Prus
2007-09-23 19:23 ` Eli Zaretskii
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=m3ps0url0j.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb-patches@sources.redhat.com \
--cc=pedro_alves@portugalmail.pt \
--cc=vladimir@codesourcery.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