archive mirror
 help / color / mirror / Atom feed
From: Derrick Stolee <>
To: Clement Moyroud <>,
	Git List <>
Subject: Re: Running scheduled maintenance in quiet mode
Date: Mon, 29 Mar 2021 15:14:58 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 3/29/2021 12:45 PM, Clement Moyroud wrote:
> Hello,
> Now that Git v2.31.0 has the fix for 'git maintenance register' on
> bare repositories, I've enabled it. I'm now getting a fairly useless
> daily e-mail with a couple of hashes listed (no other info).

Thanks for your interest in the feature! Sorry this is a
frustrating experience.

> I'd like to disable this e-mail and get the configuration to stick -
> changing my Crontab with either --quiet or a /dev/null redirect works,
> but the next time 'git maintenance start' is called, this will be
> rewritten.

You are right about that. We could alter the implementation of
'start', and the only downside is that you would need to rerun
the command to avoid those problems.

For now, you can stick to 'git maintenance register' instead of
'start' so the crontab schedule is not overwritten.

> I could not find a 'maintenance.quiet' option (or similar) in the
> config. Is there a way to do this currently?

This could also be an interesting workaround. To be distinct from
the crontab approach, it would probably be necessary to also make
the `git maintenance run --auto` output quiet by default, too.

I'm on the side of modifying the crontab schedule. I'd like to
hear other opinions before starting the work, though.


  reply	other threads:[~2021-03-29 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29 16:45 Running scheduled maintenance in quiet mode Clement Moyroud
2021-03-29 19:14 ` Derrick Stolee [this message]
2021-03-30  9:16   ` Ævar Arnfjörð Bjarmason

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).