From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [commit/6.4] Last updated date and author
Date: Tue, 22 Nov 2005 16:20:00 -0000 [thread overview]
Message-ID: <20051122084313.GJ1635@adacore.com> (raw)
In-Reply-To: <20051122080851.GG1635@adacore.com>
[-- Attachment #1: Type: text/plain, Size: 292 bytes --]
[with the patch, this time. grrrr]
This is something that I missed during the translation of gdb-6.3
to gdb-6.4 of the contents of that file... Now corrected.
2005-11-22 Joel Brobecker <brobecker@adacore.com>
* README: Update last updated date and author.
Checked in.
--
Joel
[-- Attachment #2: README.diff --]
[-- Type: text/plain, Size: 455 bytes --]
Index: README
===================================================================
RCS file: /cvs/src/src/gdb/README,v
retrieving revision 1.34.8.1
diff -u -p -r1.34.8.1 README
--- README 3 Nov 2005 01:45:06 -0000 1.34.8.1
+++ README 22 Nov 2005 08:07:09 -0000
@@ -1,5 +1,5 @@
README for gdb-6.4 release
- Updated 8, November, 2004 by Andrew Cagney
+ Updated November 22nd, 2005 by Joel Brobecker
This is GDB, the GNU source-level debugger.
prev parent reply other threads:[~2005-11-22 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 8:44 Joel Brobecker
2005-11-22 16:20 ` 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=20051122084313.GJ1635@adacore.com \
--to=brobecker@adacore.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