From: Pedro Alves <pedro_alves@portugalmail.pt>
To: Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org, eliz@gnu.org
Subject: Re: [patch] tui: initialize signal handler
Date: Sat, 22 Sep 2007 18:54:00 -0000 [thread overview]
Message-ID: <46F564A4.3000407@portugalmail.pt> (raw)
In-Reply-To: <46F54D25.3050603@linux.vnet.ibm.com>
(Eli, Apologies for misspelling you name upthread.)
Carlos Eduardo Seo wrote:
> Updated patch with your suggestions.
>
>
Thanks.
You shouldn't wrap the whole tui_initialize_win in ifdef
SIGWINCH, but it's contents instead, else on a system
without SIGWINCH, you'll get an undefined reference to
tui_initialize_win.
Other than that, it looks good to me, but, you'll need approval
from a responsible or global maintainer.
> 2007-09-22 Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
^^^ ^
It should be two spaces before and after the name.
>
> gdb/tui/tui-interp.c (tui_init): initialize
> tui's SIGWINCH signal handler.
> gdb/tui/tui-win.c (tui_initialize_win): new
> function for initializing tui's SIGWINCH signal
> handler.
> gdb/tui/tui-win.h (tui_initialize_win): added
Remove "gdb/" from the path of the changed files, since the path
is relative to the ChangeLog file location. Add "* " in front,
Capitalize the sentences and finish them with a full stop. Eg:
2007-09-22 Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
* tui/tui-interp.c (tui_init): Initialize tui's
SIGWINCH signal handler.
* tui/tui-win.c (tui_initialize_win): New.
function for initializing tui's SIGWINCH signal
handler.
* tui/tui-win.h (tui_initialize_win): Declare.
Cheers,
Pedro Alves
next prev parent reply other threads:[~2007-09-22 18:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 1:24 Carlos Eduardo Seo
2007-09-22 7:34 ` Eli Zaretskii
2007-09-22 10:44 ` Pedro Alves
2007-09-22 17:13 ` Carlos Eduardo Seo
2007-09-22 18:30 ` Eli Zaretskii
2007-09-22 18:54 ` Pedro Alves [this message]
2007-09-22 19:23 ` Carlos Eduardo Seo
2007-09-22 23:10 ` Daniel Jacobowitz
2007-09-22 23:53 ` Carlos Eduardo Seo
2007-09-29 0:10 ` Carlos Eduardo Seo
2007-09-29 0:29 ` Daniel Jacobowitz
2007-10-02 16:51 ` Ulrich Weigand
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=46F564A4.3000407@portugalmail.pt \
--to=pedro_alves@portugalmail.pt \
--cc=cseo@linux.vnet.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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