From: Joel Brobecker <brobecker@adacore.com>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: gdb's README file
Date: Thu, 03 Jun 2010 15:39:00 -0000 [thread overview]
Message-ID: <20100603153926.GL3019@adacore.com> (raw)
In-Reply-To: <4C075FE9.5050104@codesourcery.com>
> GDB's README file is quite stale, beginning with:
> README for gdb-6.3 release
> Updated 20, November, 2006
>
> this confused a user, who thought they had 6.3 sources, rather than
> more recent ones.
Yeah, this is something I had meant to work on for quite a while.
The README is updated at release time to fix the version number,
the problem is mostly with the HEAD sources.
> The attached patch removes all the 6.3ness, referring to a generic
> VERSION. I also removed the listing of the top-level directory --
> it's rather specific and I don't think useful.
I am happy with that approach. I'd give it a couple of days for people
to have a chance to comment, and then commit.
Thanks,
--
Joel
prev parent reply other threads:[~2010-06-03 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 7:56 Nathan Sidwell
2010-06-03 15:39 ` 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=20100603153926.GL3019@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=nathan@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