From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, Ronan Pigott <ronan@rjp.ie>
Subject: rp/maintenance-qol with 'make DEVELOPER=1' (was: What's cooking in git.git (Nov 2022, #03; Mon, 14))
Date: Tue, 15 Nov 2022 09:06:16 +0100 [thread overview]
Message-ID: <221115.86zgcsk5bw.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <Y3Mag8qG2D3qjlmg@nand.local>
On Mon, Nov 14 2022, Taylor Blau wrote:
> * rp/maintenance-qol (2022-11-14) 2 commits
> (merged to 'next' on 2022-11-14 at 17db40bf26)
> + maintenance: add option to register in a specific config
> + for-each-repo: interpolate repo path arguments
>
> 'git maintenance register' is taught to write configuration to an
> arbitrary path, and 'git for-each-repo' is taught to expand tilde
> characters in paths.
>
> Will cook in 'next'.
> source: <20221109190708.22725-1-ronan@rjp.ie>
$subject is broken in 'next', here's a hot-fix on top:
https://lore.kernel.org/git/patch-1.1-54d405f15f1-20221115T080212Z-avarab@gmail.com/
next prev parent reply other threads:[~2022-11-15 8:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 4:50 What's cooking in git.git (Nov 2022, #03; Mon, 14) Taylor Blau
2022-11-15 4:59 ` Eric Sunshine
2022-11-15 5:01 ` Taylor Blau
2022-11-15 6:28 ` ps/receive-use-only-advertised Patrick Steinhardt
2022-11-15 6:47 ` ps/receive-use-only-advertised Taylor Blau
2022-11-15 17:28 ` ps/receive-use-only-advertised Jeff King
2022-11-16 2:02 ` ps/receive-use-only-advertised Taylor Blau
2022-11-18 23:27 ` ps/receive-use-only-advertised Junio C Hamano
2022-11-15 8:06 ` Ævar Arnfjörð Bjarmason [this message]
2022-11-15 14:04 ` ms/sendemail-validate-headers, was Re: What's cooking in git.git (Nov 2022, #03; Mon, 14) Johannes Schindelin
2022-11-16 1:20 ` Taylor Blau
2022-11-16 11:48 ` Strawbridge, Michael
2022-11-18 13:24 ` Johannes Schindelin
2022-11-15 20:58 ` Eric Sunshine
2022-11-16 2:04 ` Taylor Blau
2022-11-16 6:07 ` Elijah Newren
2022-11-16 20:16 ` 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=221115.86zgcsk5bw.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=ronan@rjp.ie \
/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.