git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: ds/maintenance-part-[1-2] (was: What's cooking in git.git (Aug 2020, #07; Thu, 27))
Date: Fri, 28 Aug 2020 11:48:47 -0400	[thread overview]
Message-ID: <9cfbbaec-bf7d-2ed1-6b8b-0fdc8f94d094@gmail.com> (raw)
In-Reply-To: <xmqqh7snpxy1.fsf@gitster.c.googlers.com>

On 8/27/2020 5:43 PM, Junio C Hamano wrote:
> * ds/maintenance-part-2 (2020-08-25) 8 commits
>  - maintenance: add incremental-repack auto condition
>  - maintenance: auto-size incremental-repack batch
>  - maintenance: add incremental-repack task
>  - midx: use start_delayed_progress()
>  - midx: enable core.multiPackIndex by default
>  - maintenance: create auto condition for loose-objects
>  - maintenance: add loose-objects task
>  - maintenance: add prefetch task
>  (this branch uses ds/maintenance-part-1.)
> 
>  "git maintenance", an extended big brother of "git gc", continues
>  to evolve.

> * ds/maintenance-part-1 (2020-08-25) 11 commits
>  - maintenance: add trace2 regions for task execution
>  - maintenance: add auto condition for commit-graph task
>  - maintenance: use pointers to check --auto
>  - maintenance: create maintenance.<task>.enabled config
>  - maintenance: take a lock on the objects directory
>  - maintenance: add --task option
>  - maintenance: add commit-graph task
>  - maintenance: initialize task array
>  - maintenance: replace run_auto_gc()
>  - maintenance: add --quiet option
>  - maintenance: create basic maintenance runner
>  (this branch is used by ds/maintenance-part-2.)
> 
>  A "git gc"'s big brother has been introduced to take care of more
>  repository maintenance tasks, not limited to the object database
>  cleaning.
> 
>  Comments?

Thanks for calling out a call for comments here.

I appreciate all of the comments on these series. It has
really improved the feature.

I'm interested to hear who still has this on their list
to review or if there are some remaining unresolved
issues.

I sent my "RFC v3" [1] for the background portion of
maintenance, and hope to send a non-RFC version next week
if there are no more radical shifts in the strategy. Please
take a look if you are interested.

[1] https://lore.kernel.org/git/pull.680.v3.git.1598629517.gitgitgadget@gmail.com/

Thanks,
-Stolee

  parent reply	other threads:[~2020-08-28 15:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27 21:43 What's cooking in git.git (Aug 2020, #07; Thu, 27) Junio C Hamano
2020-08-27 23:34 ` Jeff King
2020-08-27 23:36   ` Junio C Hamano
2020-08-28  0:39     ` Taylor Blau
2020-08-28  6:26       ` Jeff King
2020-08-28  8:31         ` Jeff King
2020-08-28 18:09           ` Taylor Blau
2020-08-28  2:16 ` Elijah Newren
2020-08-29  4:28   ` Matheus Tavares Bernardino
2020-08-28 15:48 ` Derrick Stolee [this message]
2020-08-28 20:09 ` Hariom verma
2020-08-28 20:51   ` Junio C Hamano
2020-08-29 13:26     ` Hariom verma
2020-08-29 10:13 ` Hariom verma
2020-08-29 18:28   ` Junio C Hamano
2020-08-29 13:20     ` Hariom verma
2020-08-29 18:59       ` 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=9cfbbaec-bf7d-2ed1-6b8b-0fdc8f94d094@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).