From: "Frank Ch. Eigler" <fche@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org, gcc@gcc.gnu.org
Subject: Re: adacore git-hooks - daemon-mode email vs. systemd-logind linger
Date: Fri, 19 Apr 2024 15:28:36 -0400 [thread overview]
Message-ID: <20240419192836.GH9069@redhat.com> (raw)
In-Reply-To: <ZiLB3vdvmh9/nJmd@adacore.com>
Hi, Joel -
> [...] Thinking more long term, I think there are talks about using
> a more comprehensive system for source and contribution management,
> similar to products such as GitLab or GitHub. [...]
(Yeah, but I wouldn't count on any of that in the medium term.)
> [...] That's why I tend to think that, for the moment,
> I'd go the simplest route overall: In this case, I think the simplest
> is to just have a way to disable the daemon mode, and just have
> the users wait. In the vast majority of cases, the wait will be
> a few seconds. Even with a patch-series of a 100 patches, it would
> mean a 1min40s wait. Very bearable.
Right. the EMAIL_DELAY_IN_SECONDS time of 5s could be reduced to 1s,
or even 0.
- FChE
prev parent reply other threads:[~2024-04-19 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 10:56 Frank Ch. Eigler
2024-04-19 19:11 ` Joel Brobecker
2024-04-19 19:28 ` Frank Ch. Eigler [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=20240419192836.GH9069@redhat.com \
--to=fche@redhat.com \
--cc=brobecker@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).