list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <>
To: Junio C Hamano <>
	"Johannes Schindelin" <>,
	"Derrick Stolee" <>,
	"Nguyễn Thái Ngọc Duy" <>
Subject: Re: Preparing for 2.20.1 brown-paper-bag maintenance release
Date: Thu, 13 Dec 2018 15:05:03 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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.

  parent reply	other threads:[~2018-12-13 14:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13  6:29 Junio C Hamano
2018-12-13 12:50 ` Johannes Schindelin
2018-12-13 14:05 ` Ævar Arnfjörð Bjarmason [this message]
2018-12-13 18:08   ` Duy Nguyen
2018-12-13 18:17     ` Duy Nguyen
2018-12-14  2:40       ` 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \
    --subject='Re: Preparing for 2.20.1 brown-paper-bag maintenance release' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 git git/ \
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
 note: .onion URLs require Tor:

code repositories for project(s) associated with this inbox:

AGPL code for this site: git clone