From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: gdb-patches@sources.redhat.com
Subject: [rfa] version.in, gdb_6_1-branch
Date: Fri, 14 May 2004 17:09:00 -0000 [thread overview]
Message-ID: <20040514170913.DD2B64B104@berman.michael-chastain.com> (raw)
Here's a patch for version.in on gdb_6_1-branch.
This file somehow got whacked to zero-length on 2004-05-08.
I suspect this was a one-time problem related to the move
of sources.redhat.com and that a one-time manual patch
will be sufficient.
I tested this on native i686-pc-linux-gnu by building gdb and
observing the version number on startup.
gdb HEAD has a different problem with version.in.
I haven't looked into that yet.
Okay to commit this to gdb_6_1-branch?
Michael C
2004-05-14 Michael Chastain <mec.gnu@mindspring.com>
Fix PR build/1648.
* version.in: Fix corrupted zero-length file.
Index: version.in
===================================================================
RCS file: /cvs/src/src/gdb/version.in,v
retrieving revision 1.990.2.80
diff -c -3 -p -r1.990.2.80 version.in
*** version.in 8 May 2004 07:00:04 -0000 1.990.2.80
--- version.in 14 May 2004 16:43:04 -0000
***************
*** 0 ****
--- 1 ----
+ 6.1.0.90_2004-05-14-cvs
next reply other threads:[~2004-05-14 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 17:09 Michael Elizabeth Chastain [this message]
2004-05-14 17:49 ` Andrew Cagney
2004-05-14 18:29 Michael Elizabeth Chastain
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=20040514170913.DD2B64B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.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