From: Andrew Cagney <ac131313@redhat.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb-patches@sources.redhat.com, Jim Blandy <jimb@redhat.com>,
Elena Zannoni <ezannoni@redhat.com>
Subject: Re: [rfa] block.{c,h}
Date: Wed, 19 Feb 2003 23:15:00 -0000 [thread overview]
Message-ID: <3E541124.6010203@redhat.com> (raw)
In-Reply-To: <ro1y94b7u7o.fsf@jackfruit.Stanford.EDU>
(symtabs problem but,) some anal things.
The actual restructuring was previously ok'ed.
> +/* Code dealing with blocks for GDB.
..., the GNU debugger.
> + Copyright 2003 Free Software Foundation, Inc.
> +
> + This file is part of GDB.
> +
> + This program is free software; you can redistribute it and/or modify
> + it under the terms of the GNU General Public License as published by
> + the Free Software Foundation; either version 2 of the License, or
> + (at your option) any later version.
> +
> + This program is distributed in the hope that it will be useful,
> + but WITHOUT ANY WARRANTY; without even the implied warranty of
> + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> + GNU General Public License for more details.
> +
> + You should have received a copy of the GNU General Public License
> + along with this program; if not, write to the Free Software
> + Foundation, Inc., 59 Temple Place - Suite 330,
> + Boston, MA 02111-1307, USA. */
> +
#ifndef BLOCK_H
#define BLOCK_H
....
* Makefile.in (SFILES): block.c
``Add "block.c".''
Complete sentence, leading capital, end in fullstop. Same for others.
> * blockframe.c: Move blockvector_for_pc_sect, blockvector_for_pc,
> block_for_pc_sect, block_for_pc to block.c.
Use with the correct changelog format, function names and the like in
paren vis:
(blockvector_for_pc_sect): Moved to "block.c".
same for these.
> * symtab.c: Move block_function, contained_in to block.c.
> * frame.h: Move block_for_pc and block_for_pc_sect declarations to
> block.h. Add opaque declaration for struct block.
> * symtab.h: Move block-related stuff to block.h. Add opaque
> declarations for struct block, struct blockvector.
List them.
> * block.c: New file.
> * block.h: New file.
>
Squishing the changelog a little wouldn't hurt :-)
Andrew
next prev parent reply other threads:[~2003-02-19 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 22:59 David Carlton
2003-02-19 23:15 ` Andrew Cagney [this message]
2003-02-19 23:27 ` David Carlton
2003-02-19 23:40 ` Andrew Cagney
2003-02-19 23:49 ` David Carlton
2003-02-19 23:56 ` Andrew Cagney
2003-02-20 0:01 ` David Carlton
2003-02-19 23:36 ` 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=3E541124.6010203@redhat.com \
--to=ac131313@redhat.com \
--cc=carlton@math.stanford.edu \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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