git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Andrzej Hunt <andrzej@ahunt.org>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Jeff King <peff@peff.net>
Subject: Re: What's cooking in git.git (Sep 2021, #07; Thu, 23)
Date: Sun, 26 Sep 2021 18:00:06 +0200	[thread overview]
Message-ID: <95edb81b-f440-50eb-77e6-282de1a452d6@ahunt.org> (raw)
In-Reply-To: <xmqqa6k2yj1j.fsf@gitster.g>



On 24/09/2021 01:22, Junio C Hamano wrote:
> * ah/connect-parse-feature-v0-fix (2021-09-23) 1 commit
>   - connect: also update offset for features without values
> 
>   Protocol v0 clients can get stuck parsing a malformed feature line.
> 
>   Will merge to 'next'.
> 

I hope it's not too late - I ended up sending out a V2 at:
https://public-inbox.org/git/e1395ff2-e697-83b2-082b-d5468b7a11ac@ahunt.org/T/#md3a45bb0fdf9cfd49e0fabdb1b21cd045df523c5

The differences are:
- Peff's test (and most importantly: test stability) improvements - 
which you might already have incorporated - from 
https://public-inbox.org/git/e1395ff2-e697-83b2-082b-d5468b7a11ac@ahunt.org/T/#m5cac36b2e4aa03d452a391a3c9d2495c3a423810
- An attempt at improving the commit message, which isn't crucial.

ATB,

     Andrzej


  parent reply	other threads:[~2021-09-26 16:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23 23:22 What's cooking in git.git (Sep 2021, #07; Thu, 23) Junio C Hamano
2021-09-23 23:52 ` Taylor Blau
2021-09-24  1:30 ` Elijah Newren
2021-09-24  9:14 ` js/win-lazyload-buildfix (was Re: What's cooking in git.git (Sep 2021, #07; Thu, 23)) Carlo Marcelo Arenas Belón
2021-09-24 15:38   ` Junio C Hamano
2021-09-24 21:30   ` Johannes Sixt
2021-09-26 16:00 ` Andrzej Hunt [this message]
2021-09-27 17:33   ` What's cooking in git.git (Sep 2021, #07; Thu, 23) 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=95edb81b-f440-50eb-77e6-282de1a452d6@ahunt.org \
    --to=andrzej@ahunt.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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).