From: Andrew Cagney <ac131313@ges.redhat.com>
To: Daniel Berlin <dberlin@dberlin.org>, jimb@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: dwarf2expr.[ch]
Date: Mon, 08 Jul 2002 20:20:00 -0000 [thread overview]
Message-ID: <3D2A555C.9060500@ges.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207081941190.31676-100000@dberlin.org>
Daniel,
Just a reminder. As a GNU developer, you're expected to submit patches
that meet the GNU coding standard. This is important as it saves on
significiant run-around time spent by both yourself and the reviewer.
I guess you ment, work-in-progress.
A quick glance at this patch reveals:
> Index: dwarf2expr.c
> ===================================================================
> RCS file: dwarf2expr.c
> diff -N dwarf2expr.c
> *** /dev/null 1 Jan 1970 00:00:00 -0000
> --- dwarf2expr.c 8 Jul 2002 23:41:18 -0000
> ***************
> *** 0 ****
> --- 1,479 ----
No copyright notice.
> +
> + #include "defs.h"
> + #include "symtab.h"
> + #include "gdbtypes.h"
> + #include "elf/dwarf2.h"
> + #include "dwarf2expr.h"
Incorrectly indented function prototype (one of many). Should be ISO C.
> + struct dwarf_expr_context * new_dwarf_expr_context()
> + {
> + struct dwarf_expr_context *retval;
> + retval = xcalloc (1, sizeof (struct dwarf_expr_context));
> + return retval;
> + }
enjoy,
Andrew
next prev parent reply other threads:[~2002-07-09 3:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 16:48 Daniel Berlin
2002-07-08 20:20 ` Andrew Cagney [this message]
2002-07-08 20:49 ` Daniel Berlin
2002-07-08 21:12 ` Andrew Cagney
2002-07-09 15:21 ` Jim Blandy
2002-07-10 9:05 ` Andrew Cagney
2002-07-09 15:10 ` Jim Blandy
2002-07-09 16:00 ` Daniel Berlin
2002-07-10 11:18 ` Daniel Berlin
2002-07-10 12:48 ` Jim Blandy
2002-07-10 13:27 ` Daniel Berlin
2002-07-10 16:15 ` Jim Blandy
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=3D2A555C.9060500@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=dberlin@dberlin.org \
--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