From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2023, #03; Tue, 9)
Date: Tue, 9 May 2023 22:18:57 -0400 [thread overview]
Message-ID: <ZFr/Ef93eGZ4YKXY@nand.local> (raw)
In-Reply-To: <xmqqmt2d0x0f.fsf@gitster.g>
On Tue, May 09, 2023 at 06:56:48PM -0700, Junio C Hamano wrote:
> * tb/credential-long-lines (2023-05-01) 7 commits
> (merged to 'next' on 2023-05-02 at f027002b92)
> + contrib/credential: embiggen fixed-size buffer in wincred
> + contrib/credential: avoid fixed-size buffer in libsecret
> + contrib/credential: .gitignore libsecret build artifacts
> + contrib/credential: remove 'gnome-keyring' credential helper
> + contrib/credential: avoid fixed-size buffer in osxkeychain
> + t/lib-credential.sh: ensure credential helpers handle long headers
> + credential.c: store "wwwauth[]" values in `credential_read()`
>
> The implementation of credential helpers used fgets() over fixed
> size buffers to read protocol messages, causing the remainder of
> the folded long line to trigger unexpected behaviour, which has
> been corrected.
>
> Will merge to 'master'.
> source: <cover.1682956419.git.me@ttaylorr.com>
This has been in the "Will merge to 'master'" state for a couple of WCs.
Are you intentionally cooking it for a while in 'next' before merging,
or is this ready to go?
Thanks,
Taylor
next prev parent reply other threads:[~2023-05-10 2:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 1:56 What's cooking in git.git (May 2023, #03; Tue, 9) Junio C Hamano
2023-05-10 2:18 ` tb/pack-bitmap-index-seek Taylor Blau
2023-05-10 2:18 ` Taylor Blau [this message]
2023-05-10 7:19 ` What's cooking in git.git (May 2023, #03; Tue, 9) Teng Long
2023-05-10 16:32 ` 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=ZFr/Ef93eGZ4YKXY@nand.local \
--to=me@ttaylorr.com \
--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).