From: Johannes Sixt <j.sixt@viscovery.net>
To: Jeremiah Mahler <jmmahler@gmail.com>,
Chris Packham <judge.packham@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v3 0/9] replace signal() with sigaction()
Date: Mon, 02 Jun 2014 13:28:25 +0200 [thread overview]
Message-ID: <538C5FD9.1010706@viscovery.net> (raw)
In-Reply-To: <cover.1401645403.git.jmmahler@gmail.com>
Am 6/1/2014 20:10, schrieb Jeremiah Mahler:
> This is version 3 of the patch set to convert signal(2) to sigaction(2)
> (previous discussion [1]).
>
> [1]: http://marc.info/?l=git&m=140148352416926&w=2
>
> Changes in this revision include:
>
> - Using NULL pointers instead of 0 as per the
> Documentation/CodingGuidlines pointed out by Chris Packham.
>
> sigaction(SIGCHLD, &sa, NULL);
>
> - Conversion of all remaining files which used signal().
>
> - sigchain.c required the most changes. Both the old signal handler
> was used and the return value from signal() was being checked.
> signal() would return the previous error handler which would be
> SIG_ERR if an error occurred. sigaction() just returns -1 in this
> case.
>
> Jeremiah Mahler (9):
> compat/mingw.c: expand MinGW support for sigaction
> connect.c: replace signal() with sigaction()
> progress.c: replace signal() with sigaction()
> write_or_die.c: replace signal() with sigaction()
> daemon.c: replace signal() with sigaction()
> builtin/log.c: replace signal() with sigaction()
> builtin/merge-index.c: replace signal() with sigaction()
> builtin/verify-tag.c: replace signal() with sigaction()
> sigchain.c: replace signal() with sigaction()
The series without patch 9/9 works on Windows so far.
Without patch patch 9/9 and a more complete implementation of sigaction in
compat/mingw.c the series misses its goal. But even if you complete it, it
is IMHO only code churn without practical merits.
-- Hannes
>
> builtin/log.c | 6 +++++-
> builtin/merge-index.c | 5 ++++-
> builtin/verify-tag.c | 5 ++++-
> compat/mingw.c | 9 +++++----
> connect.c | 5 ++++-
> daemon.c | 16 +++++++++++++---
> progress.c | 6 +++++-
> sigchain.c | 14 +++++++++++---
> write_or_die.c | 6 +++++-
> 9 files changed, 56 insertions(+), 16 deletions(-)
next prev parent reply other threads:[~2014-06-02 11:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 18:10 [PATCH v3 0/9] replace signal() with sigaction() Jeremiah Mahler
2014-06-01 18:10 ` [PATCH v3 1/9] compat/mingw.c: expand MinGW support for sigaction Jeremiah Mahler
2014-06-02 5:57 ` Johannes Sixt
2014-06-01 18:10 ` [PATCH v3 2/9] connect.c: replace signal() with sigaction() Jeremiah Mahler
2014-06-01 18:10 ` [PATCH v3 3/9] progress.c: " Jeremiah Mahler
2014-06-01 18:10 ` [PATCH v3 4/9] write_or_die.c: " Jeremiah Mahler
2014-06-01 18:10 ` [PATCH v3 5/9] daemon.c: " Jeremiah Mahler
2014-06-01 18:10 ` [PATCH v3 6/9] builtin/log.c: " Jeremiah Mahler
2014-06-01 18:10 ` [PATCH v3 7/9] builtin/merge-index.c: " Jeremiah Mahler
2014-06-01 18:10 ` [PATCH v3 8/9] builtin/verify-tag.c: " Jeremiah Mahler
2014-06-01 18:10 ` [PATCH v3 9/9] sigchain.c: " Jeremiah Mahler
2014-06-02 11:28 ` Johannes Sixt [this message]
2014-06-02 14:39 ` [PATCH v3 0/9] " Jeremiah Mahler
2014-06-02 19:05 ` Junio C Hamano
2014-06-02 20:25 ` Jeremiah Mahler
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=538C5FD9.1010706@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=jmmahler@gmail.com \
--cc=judge.packham@gmail.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;
as well as URLs for NNTP newsgroup(s).