From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: [ob] correct changelog
Date: Sun, 18 Mar 2007 09:18:00 -0000 [thread overview]
Message-ID: <200703181218.27526.vladimir@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 249 bytes --]
I've noticed ChangeLog holds me responsible for
something I never checked in, and have no idea
what's that -- apparently, this is result of copy-pasting.
I've committed the attached obvious patch to
reconcile ChangeLog with "cvs log".
- Volodya
[-- Attachment #2: ChangeLog.diff --]
[-- Type: text/x-diff, Size: 596 bytes --]
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.8225
diff -u -p -r1.8225 ChangeLog
--- ChangeLog 13 Mar 2007 17:34:21 -0000 1.8225
+++ ChangeLog 18 Mar 2007 09:14:01 -0000
@@ -129,7 +129,7 @@
symbol for Ada units when the symbol is defined using 't' rather
than 'Tt' as symbol descriptor.
-2007-02-28 Vladimir Prus <vladimir@codesourcery.com>
+2007-02-28 Ulrich Weigand <uweigand@de.ibm.com>
* config/mips/tm-nbsd.h: Delete file.
* config/mips/nbsd.mt (DEPRECATED_TM_FILE): Remove.
next reply other threads:[~2007-03-18 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 9:18 Vladimir Prus [this message]
2007-03-19 16:54 ` Ulrich Weigand
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=200703181218.27526.vladimir@codesourcery.com \
--to=vladimir@codesourcery.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