From: Junio C Hamano <gitster@pobox.com>
To: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: how is maint-x.xx updated?
Date: Fri, 08 May 2020 10:53:00 -0700 [thread overview]
Message-ID: <xmqqzhaixqir.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200508172444.GA38186@Carlos-MBP> ("Carlo Marcelo Arenas Belón"'s message of "Fri, 8 May 2020 10:24:44 -0700")
Carlo Marcelo Arenas Belón <carenas@gmail.com> writes:
> While testing some potential fixes that would apply all the way to 2.17.5,
> noticed there was no official "maint-2.17" branch documented anywhere, and
> while I could obviously create my own based on the last released tag, it
> was missing the following `make test` breaking fixes:
>
> macOS: 89c0b113a0 (test: correct detection of UTF8_NFD_TO_NFC for APFS, 2018-04-30)
> NetBSD: 5826b7b595 (test-lib: check Bash version for '-x' without using shell arrays, 2019-01-03)
>
> which begs the question; is this something worth documenting?, should we care
> about maint-2.16? where is the line in the sand? can whoever is the power to
> be make sure if we ever do a 2.17.6 release to cherry-pick those 2 fixes?
I do not know where 89c0b113a0 came from; 742ae10e (test: correct
detection of UTF8_NFD_TO_NFC for APFS, 2018-04-30) smells similar.
We usually do not touch releases that old and only merge
security-relevant changes. I do not think these two qualifies.
Distros of course are free to cherry-pick on top of what we release
as v2.17.6 or whatever.
prev parent reply other threads:[~2020-05-08 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 17:24 how is maint-x.xx updated? Carlo Marcelo Arenas Belón
2020-05-08 17:53 ` Junio C Hamano [this message]
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=xmqqzhaixqir.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=carenas@gmail.com \
--cc=git@vger.kernel.org \
/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).