All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ronan Pigott <ronan@rjp.ie>
To: git@vger.kernel.org
Cc: me@ttaylor.com, derrickstolee@github.com
Subject: [PATCH v3 0/2] git-maintenance quality-of-life improvements
Date: Wed,  9 Nov 2022 12:07:06 -0700	[thread overview]
Message-ID: <20221109190708.22725-1-ronan@rjp.ie> (raw)

This is a pair of quality-of-life patches for git-maintenance that have
helped me in my workflow. PTAL.

Changes in v2:
 - Added a test case for path interpolation in for-each-repo
 - Changed [--config <file>] to [--config-file <path>] in
   register/unregister
 - Dropped the short-name option, -c
 - Avoid finding the global config when the user has supplied the config
   on the command line

Changes in v3:
 - Report an error in unregister when the user specifies a config where
   the repo is not already registered
 - Add a test case for the above
 - Correct option description in the docs

Ronan Pigott (2):
  for-each-repo: interpolate repo path arguments
  maintenance: add option to register in a specific config

 Documentation/git-maintenance.txt | 14 +++++-----
 builtin/for-each-repo.c           |  5 +++-
 builtin/gc.c                      | 45 ++++++++++++++++++++++---------
 t/t0068-for-each-repo.sh          |  6 +++++
 t/t7900-maintenance.sh            | 21 ++++++++++++++-
 5 files changed, 69 insertions(+), 22 deletions(-)

-- 
2.38.1


             reply	other threads:[~2022-11-09 19:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 19:07 Ronan Pigott [this message]
2022-11-09 19:07 ` [PATCH v3 1/2] for-each-repo: interpolate repo path arguments Ronan Pigott
2022-11-09 19:07 ` [PATCH v3 2/2] maintenance: add option to register in a specific config Ronan Pigott
2022-11-09 21:25 ` [PATCH v3 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:
  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=20221109190708.22725-1-ronan@rjp.ie \
    --to=ronan@rjp.ie \
    --cc=derrickstolee@github.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylor.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.