{"thread":{"id":"53434","subject":"how is maint-x.xx updated?","startedAt":"2020-05-08T17:24:50Z","lastAt":"2020-05-08T17:53:06Z","messageCount":2,"participants":["Carlo Marcelo Arenas Belón","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"397427","messageId":"20200508172444.GA38186@Carlos-MBP","threadId":"53434","inReplyTo":null,"subject":"how is maint-x.xx updated?","fromName":"Carlo Marcelo Arenas Belón","fromEmail":"carenas@gmail.com","sentAt":"2020-05-08T17:24:44Z","receivedAt":"2020-05-08T17:24:50Z","isPatch":false,"sender":{"key":"carenas@gmail.com","avatar":"https://avatars.githubusercontent.com/u/76036?v=4"},"body":"While testing some potential fixes that would apply all the way to 2.17.5,\nnoticed there was no official \"maint-2.17\" branch documented anywhere, and\nwhile I could obviously create my own based on the last released tag, it\nwas missing the following `make test` breaking fixes:\n\n  macOS: 89c0b113a0 (test: correct detection of UTF8_NFD_TO_NFC for APFS, 2018-04-30)\n  NetBSD: 5826b7b595 (test-lib: check Bash version for '-x' without using shell arrays, 2019-01-03)\n\nwhich begs the question; is this something worth documenting?, should we care\nabout maint-2.16? where is the line in the sand? can whoever is the power to\nbe make sure if we ever do a 2.17.6 release to cherry-pick those 2 fixes?\n\nCarlo\n"},{"id":"397429","messageId":"xmqqzhaixqir.fsf@gitster.c.googlers.com","threadId":"53434","inReplyTo":"20200508172444.GA38186@Carlos-MBP","subject":"Re: how is maint-x.xx updated?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2020-05-08T17:53:00Z","receivedAt":"2020-05-08T17:53:06Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Carlo Marcelo Arenas Belón <carenas@gmail.com> writes:\n\n> While testing some potential fixes that would apply all the way to 2.17.5,\n> noticed there was no official \"maint-2.17\" branch documented anywhere, and\n> while I could obviously create my own based on the last released tag, it\n> was missing the following `make test` breaking fixes:\n>\n>   macOS: 89c0b113a0 (test: correct detection of UTF8_NFD_TO_NFC for APFS, 2018-04-30)\n>   NetBSD: 5826b7b595 (test-lib: check Bash version for '-x' without using shell arrays, 2019-01-03)\n>\n> which begs the question; is this something worth documenting?, should we care\n> about maint-2.16? where is the line in the sand? can whoever is the power to\n> be make sure if we ever do a 2.17.6 release to cherry-pick those 2 fixes?\n\nI do not know where 89c0b113a0 came from; 742ae10e (test: correct\ndetection of UTF8_NFD_TO_NFC for APFS, 2018-04-30) smells similar.\n\nWe usually do not touch releases that old and only merge\nsecurity-relevant changes.  I do not think these two qualifies.\n\nDistros of course are free to cherry-pick on top of what we release\nas v2.17.6 or whatever.\n\n"}]}