All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: ds/maintenance-part-1 (was Re: What's cooking in git.git (Sep 2020, #04; Wed, 16))
Date: Thu, 17 Sep 2020 08:54:30 -0400	[thread overview]
Message-ID: <39e940da-c8ee-9371-84e3-1bedbe86bf5b@gmail.com> (raw)
In-Reply-To: <xmqq8sd9t679.fsf@gitster.c.googlers.com>

On 9/16/2020 11:47 PM, Junio C Hamano wrote:
> * ds/maintenance-part-1 (2020-09-06) 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 and ds/maintenance-part-3.)
> 
>  A "git gc"'s big brother has been introduced to take care of more
>  repository maintenance tasks, not limited to the object database
>  cleaning.
> 
>  On hold.
>  cf. <0b35829f-a83b-a093-2dc5-0e7d3b42fd15@gmail.com>

This message [1] includes a simple forward-fix for the
parsing logic. I mention a re-roll in my preface, but
I was talking about a potential re-roll of part-3 when
that gets more feedback.

My hope was that the quick fix could be applied directly
on top of this branch and then cook in next as planned.
I'll accept a delay if you think that is merited, but "on
hold" just seems like you are waiting for something more
from me.

Thanks,
-Stolee

[1] https://lore.kernel.org/git/0b35829f-a83b-a093-2dc5-0e7d3b42fd15@gmail.com/

  reply	other threads:[~2020-09-17 12:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17  3:47 What's cooking in git.git (Sep 2020, #04; Wed, 16) Junio C Hamano
2020-09-17 12:54 ` Derrick Stolee [this message]
2020-09-17 16:36   ` ds/maintenance-part-1 (was Re: What's cooking in git.git (Sep 2020, #04; Wed, 16)) Junio C Hamano
2020-09-17 17:37     ` Derrick Stolee
2020-09-17 19:52 ` What's cooking in git.git (Sep 2020, #04; Wed, 16) Junio C Hamano
2020-09-17 21:39 ` Junio C Hamano
2020-09-20 17:02   ` Johannes Schindelin

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=39e940da-c8ee-9371-84e3-1bedbe86bf5b@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.