From: David Relson <relson@osagesoftware.com>
To: gdb@sources.redhat.com
Subject: Re: 5.1 ERRATA file?
Date: Sat, 17 Nov 2001 10:40:00 -0000 [thread overview]
Message-ID: <4.3.2.7.2.20011127094533.00b39dc0@mail.osagesoftware.com> (raw)
In-Reply-To: <3C033A28.50209@cygnus.com>
At 02:00 AM 11/27/01, Andrew Cagney wrote:
>Something I noticed from the feedback so far is that it is hard to know
>what problems a release will have - they are burried in the file
>gdb/README. What do people think of them being moved to the file
>gdb/ERRATA? Then again, the GNU coding standard might override such an
>idea :-/
Andrew,
I like the idea. The name ERRATA is clear and, as with all files with
all-caps in their names, it stands out in a directory listing.
David
WARNING: multiple messages have this Message-ID
From: David Relson <relson@osagesoftware.com>
To: gdb@sources.redhat.com
Subject: Re: 5.1 ERRATA file?
Date: Tue, 27 Nov 2001 06:47:00 -0000 [thread overview]
Message-ID: <4.3.2.7.2.20011127094533.00b39dc0@mail.osagesoftware.com> (raw)
Message-ID: <20011127064700._ioOE6CvaMuG2hSvCIvmkzksBL1Cbe1TgBdPJJiu7OU@z> (raw)
In-Reply-To: <3C033A28.50209@cygnus.com>
At 02:00 AM 11/27/01, Andrew Cagney wrote:
>Something I noticed from the feedback so far is that it is hard to know
>what problems a release will have - they are burried in the file
>gdb/README. What do people think of them being moved to the file
>gdb/ERRATA? Then again, the GNU coding standard might override such an
>idea :-/
Andrew,
I like the idea. The name ERRATA is clear and, as with all files with
all-caps in their names, it stands out in a directory listing.
David
next prev parent reply other threads:[~2001-11-27 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 7:37 Andrew Cagney
2001-11-16 9:42 ` Eli Zaretskii
2001-11-26 23:41 ` Eli Zaretskii
2001-11-27 5:03 ` gdb
2001-11-17 8:54 ` gdb
2001-11-19 3:12 ` Andrew Cagney
2001-11-27 23:15 ` Andrew Cagney
2001-11-17 10:40 ` David Relson [this message]
2001-11-27 6:47 ` David Relson
2001-11-26 23:01 ` Andrew Cagney
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=4.3.2.7.2.20011127094533.00b39dc0@mail.osagesoftware.com \
--to=relson@osagesoftware.com \
--cc=gdb@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