git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Preparing for 2.20.1 brown-paper-bag maintenance release

From
Duy Nguyen <pclouds@gmail.com>
Date
Dec 13, 2018, 18:08 UTC
Message-ID
<CACsJy8AB0gQAvAWh3vtiSFnZWXtdvQdi4czBoR2B8TkECMrQtQ@mail.gmail.com>
In-Reply-To
<87r2el1q0g.fsf@evledraar.gmail.com>

On Thu, Dec 13, 2018 at 3:05 PM Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:

Show 28 quoted lines
>
>
> On Thu, Dec 13 2018, Junio C Hamano wrote:
>
> > Here is an excerpt from a draft edition of "What's cooking" report
> > for topics that are about an immediate 2.20.1 maintenance release,
> > with five topics that I plan to merge to 'next' and then to 'maint'
> > soonish (they're all marked as "Will merge to 'next' and then to
> > 'master'").
> >
> > They'll be in 'pu' but not in 'next' in today's pushout, but unless
> > I hear breakage reports in time, I am hoping to merge them to 'next'
> > during tomorrow's integration cycle, so that we can start the new
> > week with 2.20.1.
> > [...]
> > * nd/show-gitcomp-compilation-fix (2018-12-12) 1 commit
> >  - parse-options: fix SunCC compiler warning
> >
> >  Portability fix for a recent update to parse-options API.
>
> Since I reported this, just a clarification: Unlike 46c0eb5843
> ("files-backend.c: fix build error on Solaris", 2018-11-25) this one's
> not an error on suncc, just a warning (and we have 20-30 of those exact
> warnings in our code).
>
> So if you wanted to minimize 2.20.1 this could be held back, but also it
> looks obviously correct so it's fine that it makes it into that point
> release. Just FYI.

There's also a bug in my patch (-2 is already being used by parse_opt_unknown_cb and my patch will change behavior of git-blame at least in theory). I'll reroll later. I think it's better to hold it back.

-- 
Duy
Previous: Ævar Arnfjörð BjarmasonNext: Duy Nguyen
Message 4 of 6 in “Preparing for 2.20.1 brown-paper-bag maintenance release”
  1. Junio C HamanoDec 13, 2018
  2. Johannes SchindelinDec 13, 2018
  3. Ævar Arnfjörð BjarmasonDec 13, 2018
  4. Duy NguyenDec 13, 2018
  5. Duy NguyenDec 13, 2018
  6. Junio C HamanoDec 14, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.