From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Robert Lupton the Good <rhl@astro.princeton.edu>
Cc: gdb@sourceware.org
Subject: Re: Patch to add argument parsing classes to gdb
Date: Sun, 13 Nov 2011 13:29:00 -0000 [thread overview]
Message-ID: <m3lirkkv5z.fsf@redhat.com> (raw)
In-Reply-To: <412F240F-46E7-4A5C-8207-721E15A58B6D@astro.princeton.edu> (Robert Lupton the Good's message of "Fri, 11 Nov 2011 14:38:33 -0500")
Hi Robert,
Robert Lupton the Good <rhl@astro.princeton.edu> writes:
> I'm attaching a patch that implements two classes, GdbOptionParser and
> GdbArgumentParser, which are built around python's standard optparse
> and argparse but play well with gdb (e.g. don't call exit if you make
> a typo or ask for help!). The code imports with python >= 2.3, but
> only provides the argparse-based parser if you actually have argparse
> in your path (python == 2.7?).
>
> The patch:
> Implements the classes
> Adds docs
> Adds test cases
>
> What else do you need to get this into the source tree? I'm not sure
> how to deal with copyright assignment.
The right place to submit patches is not this list. You should rather
use gdb-patches@sourceware.org. About copyright assignment, I can send
you the form if you want.
Also, you need to write a ChangeLog entry for this. And I'd suggest
cleaning the patch a bit, because it contains some useless lines like:
> ? .deps
> cvs diff: Diffing .
> Index: utils.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/utils.c,v
> retrieving revision 1.265
> diff -a -c -w -r1.265 utils.c
> *** utils.c 4 Nov 2011 16:45:12 -0000 1.265
> --- utils.c 11 Nov 2011 19:20:09 -0000
> ***************
> *** 729,736 ****
> --- 729,740 ----
> struct timeval now_wall_time, delta_wall_time;
>
> gettimeofday (&now_wall_time, NULL);
> + #if 0 /* no timeval_sub */
> timeval_sub (&delta_wall_time,
> &now_wall_time, &start_stats->start_wall_time);
> + #else
> + delta_wall_time.tv_sec = delta_wall_time.tv_usec = 0; /* HACK */
> + #endif
If this is a hack, then it should be fixed before submitting the patch.
Have you run a regression test against this patch? It is a common
practice, and should be always done.
Otherwise, thanks for the work.
prev parent reply other threads:[~2011-11-13 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 19:38 Robert Lupton the Good
2011-11-13 13:29 ` Sergio Durigan Junior [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=m3lirkkv5z.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb@sourceware.org \
--cc=rhl@astro.princeton.edu \
/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