From: Eli Zaretskii <eliz@is.elta.co.il>
To: Mark Kettenis <kettenis@wins.uva.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Unified watchpoints for x86 platforms
Date: Sun, 18 Mar 2001 00:57:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1010318105304.11615A-100000@is> (raw)
In-Reply-To: <200103172253.f2HMrg509595@delius.kettenis.local>
On Sat, 17 Mar 2001, Mark Kettenis wrote:
> Oh, by the way, I don't think it's necessary to list changes for newly
> added files to the ChangeLog. Just something like:
>
> * i386-nat.c: New file.
>
> should be enough.
I know. But does it hurt to have the new functions listed as well?
I was always annoyed by the fact that the first functions on each file
need to be deduced by elimination, instead of just reading the logs.
For example, imagine that you want to know when was a certain function
introduced.
next prev parent reply other threads:[~2001-03-18 0:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200103032150.QAA29021@indy.delorie.com>
2001-03-07 1:20 ` Eli Zaretskii
2001-03-07 7:56 ` Mark Kettenis
2001-03-07 9:23 ` Eli Zaretskii
2001-03-09 14:05 ` Mark Kettenis
2001-03-11 3:19 ` Eli Zaretskii
2001-03-14 5:11 ` Mark Kettenis
2001-03-17 9:18 ` Eli Zaretskii
2001-03-17 14:54 ` Mark Kettenis
2001-03-18 0:57 ` Eli Zaretskii [this message]
2001-03-17 15:20 ` Mark Kettenis
2001-03-18 0:58 ` Eli Zaretskii
2001-03-18 12:47 ` [RFA] Make access watchpoints work again Eli Zaretskii
2001-03-19 8:56 ` Andrew Cagney
2001-03-20 1:54 ` Eli Zaretskii
2001-03-23 8:06 ` Andrew Cagney
2001-03-17 9:21 ` [RFA] Unified watchpoints for x86 platforms Eli Zaretskii
[not found] <200103182306.f2IN6Fv00262@delius.kettenis.local>
2001-03-21 3:42 ` Eli Zaretskii
2001-03-21 3:43 ` Eli Zaretskii
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=Pine.SUN.3.91.1010318105304.11615A-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@wins.uva.nl \
/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