mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Taylor Blau <>
To: Derrick Stolee <>
Cc: Ronan Pigott <>,,
Subject: Re: [PATCH v2 2/2] maintenance: add option to register in a specific config
Date: Wed, 9 Nov 2022 21:38:42 -0500	[thread overview]
Message-ID: <Y2xkMnQQ4w8rhSwD@nand.local> (raw)
In-Reply-To: <>

On Wed, Nov 09, 2022 at 10:05:32AM -0500, Derrick Stolee wrote:
> On 11/8/2022 2:49 PM, Ronan Pigott wrote:
> > maintenance register currently records the maintenance repo exclusively
> > within the user's global configuration, but other configuration files
> > may be relevant when running maintenance if they are included from the
> > global config. This option allows the user to choose where maintenance
> > repos are recorded.
> > +	Initialize Git config values so any scheduled maintenance will start
> > +	running on this repository. This adds the repository to the
> > +	`maintenance.repo` config variable in the current user's global config,
> > +	or the config specified by --config option, and enables some
> This still says --config...

Thanks for spotting. I graduated this topic too early, it seems. Let's
hold it in 'next' while we wait for a patch or two on top, or I can see
about reverting what's in 'next' and replacing it with a new round.


  reply	other threads:[~2022-11-10  2:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 19:49 [PATCH v2 0/2] git-maintenance quality-of-life improvements Ronan Pigott
2022-11-08 19:49 ` [PATCH v2 1/2] for-each-repo: interpolate repo path arguments Ronan Pigott
2022-11-08 19:49 ` [PATCH v2 2/2] maintenance: add option to register in a specific config Ronan Pigott
2022-11-08 20:38   ` Phillip Wood
2022-11-08 20:57     ` Taylor Blau
2022-11-08 21:28       ` Phillip Wood
2022-11-08 22:45       ` ronan
2022-11-09 15:05   ` Derrick Stolee
2022-11-10  2:38     ` Taylor Blau [this message]
2022-11-08 19:54 ` [PATCH v2 0/2] git-maintenance quality-of-life improvements Taylor Blau

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:

  List information:

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

  git send-email \
    --in-reply-to=Y2xkMnQQ4w8rhSwD@nand.local \ \ \ \ \ \

* 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

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