From: Patrick Steinhardt <ps@pks.im>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2024, #10; Tue, 22)
Date: Wed, 23 Oct 2024 08:17:03 +0200 [thread overview]
Message-ID: <ZxiU1mw1mbRaxoRO@pks.im> (raw)
In-Reply-To: <ZxgUocb5gH+zuKRw@nand.local>
On Tue, Oct 22, 2024 at 05:09:53PM -0400, Taylor Blau wrote:
> * rj/cygwin-exit (2024-10-18) 1 commit
> - credential-cache: treat ECONNABORTED like ECONNRESET
>
> Treat ECONNABORTED the same as ECONNRESET in 'git credential-cache' to
> work around a possible Cygwin regression. This resolves a race condition
> caused by changes in Cygwin's handling of socket closures, allowing the
> client to exit cleanly when encountering ECONNABORTED.
>
> Will merge to 'next'?
> source: <20241018052952.GE2408674@coredump.intra.peff.net>
I think this one should be ready to go.
> * sa/notes-edit (2024-10-21) 1 commit
> - notes: teach the -e option to edit messages in editor
>
> Teach 'git notes add' and 'git notes append' a new '-e' flag,
> instructing them to open the note in $GIT_EDITOR before saving.
>
> Needs review.
> source: <pull.1817.v4.git.1729534340786.gitgitgadget@gmail.com>
I've just reviewed this and think that the topic is ready to go, as
well.
> * ss/duplicate-typos (2024-10-21) 1 commit
> - global: Fix duplicate word typos
>
> Typofixes.
>
> Will merge to 'next'?
> source: <6ce47185-690d-415e-95c9-06a3b828be29e@cs-ware.de>
Looks ready to me.
Patrick
next prev parent reply other threads:[~2024-10-23 6:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 21:09 What's cooking in git.git (Oct 2024, #10; Tue, 22) Taylor Blau
2024-10-23 6:17 ` Patrick Steinhardt [this message]
2024-10-23 20:18 ` 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=ZxiU1mw1mbRaxoRO@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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 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 NNTP newsgroup(s).