From: Michael McClimon <michael@mcclimon.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2022, #06; Wed, 19)
Date: Thu, 20 Oct 2022 21:16:38 -0400 [thread overview]
Message-ID: <Y1Hy9n7E1/yWKkYv@newk> (raw)
In-Reply-To: <xmqqa65rnuvv.fsf@gitster.g>
> * mm/git-pm-try-catch-syntax-fix (2022-10-17) 1 commit
> - Git.pm: add semicolon after catch statement
>
> Fix a longstanding syntax error in Git.pm error codepath.
>
> Will merge to 'next'??
> source: <20221016212236.12453-2-michael@mcclimon.org>
I am not totally sure what these question marks mean, but I'm happy for
this to go to next, for what it's worth. (There was an outstanding
question about the general behavior of Git.pm in bare unsafe
repositories, but I certainly am not planning to solve it in this
series.) Thanks!
--
Michael McClimon
michael@mcclimon.org
next prev parent reply other threads:[~2022-10-21 1:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 1:31 What's cooking in git.git (Oct 2022, #06; Wed, 19) Junio C Hamano
2022-10-20 6:18 ` Jeff King
2022-10-20 15:38 ` Junio C Hamano
2022-10-20 9:56 ` pw/rebase-reflog-fixes (was Re: What's cooking in git.git (Oct 2022, #06; Wed, 19)) Phillip Wood
2022-10-21 1:16 ` Michael McClimon [this message]
2022-10-21 4:55 ` What's cooking in git.git (Oct 2022, #06; Wed, 19) Jeff King
2022-10-21 19:45 ` Glen Choo
2022-10-22 22:11 ` Jeff King
2022-10-21 3:15 ` tb/remove-unused-pack-bitmap Taylor Blau
-- strict thread matches above, loose matches on Subject: below --
2022-10-20 1:34 What's cooking in git.git (Oct 2022, #06; Wed, 19) Junio C Hamano
2022-10-20 11:57 ` Philip Oakley
2022-10-20 15:35 ` 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=Y1Hy9n7E1/yWKkYv@newk \
--to=michael@mcclimon.org \
--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).