list mirror (unofficial, one of many)
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <>
To: Junio C Hamano <>
	Johannes Schindelin <>
Subject: Git v2.21.0-rc0 broken on *BSD, maybe others
Date: Tue, 12 Feb 2019 13:13:35 +0100
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, Feb 07 2019, Junio C Hamano wrote:

> An early preview release Git v2.21.0-rc0 is now available for
> testing at the usual places.  It is comprised of 426 non-merge
> commits since v2.20.0, contributed by 57 people, 13 of which are
> new faces.

As seen on there are
regressions since 2.19.0, e.g. we have hard compile errors on BSD now,
and maybe AIX. I haven't dug into it.

I probably won't have the time for this myself before 2.21, but am
sending this message in case others are interested. I don't expect these
to be serious issues, just portability nits that'll either be fixed
before 2.21, or alternatively by people packaging for those
platforms. If they don't care enough to pursue it pro-actively I'm not
very inclined to spend time on it myself...

Johannes: We didn't have a chance to finish this conversation up at Git
Merge, but the useful bit of CI platforms basically devolves into
test_for(SHA1, params), with the hard part driving it so it's done
constantly, N branches are tested with smart notices of "XYZ broken in A
but not B" etc.

My impression is that you're *way* ahead with the Azure stuff for
solving those hard parts. Is there any way we could ditch most of this
ad-hoc GitLab CI setup I have on the GCC compile farm, and make it be
driven by what you have, and at some point it would just do something

    ssh <some compile farm host> " SHA1 <params>"

Then we could all display it in the same UI, and get feedback on "pu"
topics before they land et.c

  parent reply	other threads:[~2019-02-12 12:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07  7:28 [ANNOUNCE] Git v2.21.0-rc0 Junio C Hamano
2019-02-07 12:39 ` Christian Couder
2019-02-07 19:47 ` Johannes Schindelin
2019-02-07 19:50 ` Johannes Schindelin
2019-02-07 20:34   ` Junio C Hamano
2019-02-07 20:56     ` Junio C Hamano
2019-02-12 12:13 ` Ævar Arnfjörð Bjarmason [this message]
2019-02-12 12:43   ` Git v2.21.0-rc0 broken on *BSD, maybe others Duy Nguyen
2019-02-12 12:45     ` Duy Nguyen
2019-02-12 13:14       ` Ævar Arnfjörð Bjarmason
2019-02-12 13:16         ` Ævar Arnfjörð Bjarmason
2019-02-12 13:30         ` SZEDER Gábor
2019-02-13 14:56           ` Johannes Schindelin
2019-02-12 17:07     ` Junio C Hamano
2019-02-12 18:41       ` Junio C Hamano
2019-02-12 18:42       ` Junio C Hamano
2019-02-12 17:52     ` Junio C Hamano
2019-02-12 17:56       ` Junio C Hamano
2019-02-12 12:44   ` SZEDER Gábor
2019-02-12 13:07     ` Ævar Arnfjörð Bjarmason

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 \ \ \ \ \ \ \

* 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 the project(s) associated with this inbox:

AGPL code for this site: git clone