From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: ds/maintenance-part-3 (was Re: What's cooking in git.git (Nov 2020, #02; Mon, 9))
Date: Tue, 10 Nov 2020 08:31:35 -0500 [thread overview]
Message-ID: <d0123439-236c-1a62-294b-a3373465eadb@gmail.com> (raw)
In-Reply-To: <xmqq7dqu9jwh.fsf@gitster.c.googlers.com>
On 11/9/2020 6:42 PM, Junio C Hamano wrote:
> * ds/maintenance-part-3 (2020-10-16) 8 commits
> - maintenance: add troubleshooting guide to docs
> - maintenance: use 'incremental' strategy by default
> - maintenance: create maintenance.strategy config
> - maintenance: add start/stop subcommands
> - maintenance: add [un]register subcommands
> - for-each-repo: run subcommands on configured repos
> - maintenance: add --schedule option and config
> - maintenance: optionally skip --auto process
> (this branch is used by ds/maintenance-part-4.)
>
> Parts of "git maintenance" to ease writing crontab entries (and
> other scheduling system configuration) for it.
>
> Will merge to 'next'?
This hasn't changed for a while, and part-4 is also sitting
after some initial feedback. I'd love for others to test
these background maintenance activities in their home forks.
I certainly have on all three platforms.
Perhaps part-3 could merge to 'next' soonish? I know we
discussed only merging part-3 and part-4 to 'master' at the
same time, but it would be good to have part-3 start cooking
in 'next' sooner than later, right?
Thanks,
-Stolee
next prev parent reply other threads:[~2020-11-10 13:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 23:42 What's cooking in git.git (Nov 2020, #02; Mon, 9) Junio C Hamano
2020-11-10 0:44 ` Elijah Newren
2020-11-10 1:03 ` Jeff King
2020-11-10 13:31 ` Derrick Stolee [this message]
2020-11-16 23:56 ` ds/maintenance-part-3 (was Re: What's cooking in git.git (Nov 2020, #02; Mon, 9)) Emily Shaffer
2020-11-17 0:40 ` Junio C Hamano
2020-11-17 1:07 ` Emily Shaffer
2020-11-17 13:56 ` Derrick Stolee
2020-11-17 19:18 ` Emily Shaffer
2020-11-17 19:34 ` Junio C Hamano
2020-11-17 21:12 ` Derrick Stolee
2020-11-19 2:16 ` Junio C Hamano
2020-11-19 13:25 ` Derrick Stolee
2020-11-19 15:53 ` Derrick Stolee
2020-11-19 18:06 ` Junio C Hamano
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=d0123439-236c-1a62-294b-a3373465eadb@gmail.com \
--to=stolee@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).