From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Noam Postavsky <npostavs@users.sourceforge.net>, git@vger.kernel.org
Subject: Re: git-credential-cache--daemon quits on SIGHUP, can we change it to ignore instead?
Date: Fri, 04 Dec 2015 10:55:32 -0800 [thread overview]
Message-ID: <xmqqpoymrql7.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20151110122501.GA14418@sigill.intra.peff.net> (Jeff King's message of "Tue, 10 Nov 2015 07:25:02 -0500")
Jeff King <peff@peff.net> writes:
>> diff --git a/credential-cache--daemon.c b/credential-cache--daemon.c
>> index eef6fce..6cda9c0 100644
>> --- a/credential-cache--daemon.c
>> +++ b/credential-cache--daemon.c
>> @@ -256,6 +256,9 @@ int main(int argc, const char **argv)
>> OPT_END()
>> };
>>
>> + int ignore_sighup = 0;
>> + git_config_get_bool("credentialcache.ignoresighup", &ignore_sighup);
>> +
>
> Style-wise, I think the declaration should go above the options-list.
I was about to merge this to 'master', following your last issue of
"What's cooking" report.
I was puzzled that git_config_get_bool() is used here without even
checking if we are inside any Git repository and wondered if it was
correct. I'd imagine this is not a problem, as this process is
spawned by "credential-cache" that was spawned by somebody (either
push or fetch) who has read $GIT_DIR/config for credential.helper to
determine that credential-cache needs to be used.
>> @@ -264,6 +267,10 @@ int main(int argc, const char **argv)
>>
>> check_socket_directory(socket_path);
>> register_tempfile(&socket_file, socket_path);
>> +
>> + if (ignore_sighup)
>> + signal(SIGHUP, SIG_IGN);
>> +
>
> This part looks obviously correct. :)
>
> I don't think there's any need to use sigchain_push here (we have no
> intention of ever popping it).
>
> -Peff
next prev parent reply other threads:[~2015-12-04 18:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 16:45 git-credential-cache--daemon quits on SIGHUP, can we change it to ignore instead? Noam Postavsky
2015-10-18 15:15 ` Noam Postavsky
2015-10-18 17:58 ` Junio C Hamano
2015-10-19 0:51 ` Noam Postavsky
2015-10-21 2:35 ` Noam Postavsky
2015-10-24 21:47 ` Noam Postavsky
2015-10-25 16:58 ` Junio C Hamano
2015-10-26 21:50 ` Jeff King
2015-10-27 0:50 ` Noam Postavsky
2015-10-27 18:41 ` Jeff King
2015-10-27 19:04 ` Junio C Hamano
2015-10-27 17:52 ` Junio C Hamano
2015-10-27 18:47 ` Jeff King
2015-10-28 3:46 ` Noam Postavsky
2015-10-30 0:10 ` Jeff King
2015-10-30 0:43 ` Noam Postavsky
2015-10-30 0:50 ` Jeff King
2015-10-30 1:20 ` Noam Postavsky
2015-10-30 21:08 ` Jeff King
2015-11-09 2:58 ` Noam Postavsky
2015-11-09 15:53 ` Jeff King
2015-11-10 1:05 ` Noam Postavsky
2015-11-10 12:25 ` Jeff King
2015-11-10 12:26 ` Jeff King
2015-11-11 0:22 ` Noam Postavsky
2015-12-04 18:55 ` Junio C Hamano [this message]
2015-12-04 19:06 ` Jeff King
2015-12-04 20:05 ` Junio C Hamano
2015-12-04 23:25 ` Jeff King
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=xmqqpoymrql7.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=npostavs@users.sourceforge.net \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.