From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <derrickstolee@github.com>
Cc: Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, vdye@github.com
Subject: Re: [PATCH 3/3] scalar: only warn when background maintenance fails
Date: Fri, 27 Jan 2023 16:32:03 -0800 [thread overview]
Message-ID: <xmqq357v8poc.fsf@gitster.g> (raw)
In-Reply-To: <4913381a-769f-aba0-c04d-559d103e8396@github.com> (Derrick Stolee's message of "Fri, 27 Jan 2023 17:18:23 -0500")
Derrick Stolee <derrickstolee@github.com> writes:
>> The "maintain
>> their clone" certainly should include running periodic maintenance
>> tasks without them having to worry about it. It feels like this is
>> calling for an explicit "disable periodic maintenance tasks in this
>> repository" option to help these esoteric environments that disable
>> cron-like system services, while keeping the default safer,
>> i.e. fail loudly when the periodic maintenance tasks that the users
>> expect to happen cannot be enabled, or something.
>>
>> Perhaps I am not the primary audience, but hmph, I have a feeling
>> that this is not exactly going into a healthy direction.
>
> Here, we are in an environment where background maintenance is
> unavailable in an unexpected way. If that feature is not available
> to the user, should they not get the benefits of the others?
That is not what I was saying. I just have expected to see a way
for the user to give scalar an explicit "I understand that periodic
maintenance does not happen in this repository" consent, instead of
demoting an error detection for everybody to a warning that users
will just ignore.
next prev parent reply other threads:[~2023-01-28 0:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 20:06 [PATCH 0/3] Allow scalar to succeed despite maintenance failures Derrick Stolee via GitGitGadget
2023-01-27 20:06 ` [PATCH 1/3] t: allow 'scalar' in test_must_fail Derrick Stolee via GitGitGadget
2023-01-27 20:06 ` [PATCH 2/3] t921*: test scalar behavior starting maintenance Derrick Stolee via GitGitGadget
2023-01-27 20:06 ` [PATCH 3/3] scalar: only warn when background maintenance fails Derrick Stolee via GitGitGadget
2023-01-27 20:36 ` Junio C Hamano
2023-01-27 22:18 ` Derrick Stolee
2023-01-28 0:32 ` Junio C Hamano [this message]
2023-01-30 13:44 ` Derrick Stolee
2023-01-30 15:40 ` Junio C Hamano
2023-01-30 17:42 ` Victoria Dye
2023-01-30 18:58 ` Junio C Hamano
2023-01-30 19:06 ` Derrick Stolee
2023-01-27 22:18 ` Victoria Dye
2023-01-30 19:25 ` Derrick Stolee
2023-01-27 22:06 ` Victoria Dye
2023-01-27 22:14 ` Derrick Stolee
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq357v8poc.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=vdye@github.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).