All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: rsbecker@nexbridge.com, git@vger.kernel.org,
	git-packagers@googlegroups.com
Subject: Re: v2.37.0-rc2 - Additional Breakages on NonStop x86 (was RE: [ANNOUNCE] Git v2.37.0-rc2)
Date: Thu, 23 Jun 2022 09:27:58 -0700	[thread overview]
Message-ID: <xmqqmte31h0x.fsf@gitster.g> (raw)
In-Reply-To: <664fcc55-1cd3-eb01-9be6-80bc4492e849@web.de> ("René Scharfe"'s message of "Thu, 23 Jun 2022 17:21:46 +0200")

René Scharfe <l.s.r@web.de> writes:

> Am 23.06.22 um 14:55 schrieb rsbecker@nexbridge.com:
>> RC2 had numerous new test failures on NonStop that were not
>> present in RC1, RC0, or prior git releases, ignoring the @2
>> problem previously reported.

I am wondering if "@2 problem" is the only thing that were present
in -rc1 but was only noticed in -rc2, which presumably is because
some other changes in the reporter's build and test environment.

> rc2 changed the following files:
>
>    $ git diff --stat v2.37.0-rc1 v2.37.0-rc2
>     Documentation/git-gc.txt         |  3 +--
>     GIT-VERSION-GEN                  |  2 +-
>     builtin/name-rev.c               |  2 +-
>     contrib/completion/git-prompt.sh | 32 +++++++++++++++++---------------
>     t/t9903-bash-prompt.sh           |  2 +-
>     5 files changed, 21 insertions(+), 20 deletions(-)
>
> The name-rev change only modifies a help message.  At first glance there
> doesn't seem to be a way that these changes may influence the outcome of
> those tests.

Thanks for a thought.

      parent reply	other threads:[~2022-06-23 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23 12:55 v2.37.0-rc2 - Additional Breakages on NonStop x86 (was RE: [ANNOUNCE] Git v2.37.0-rc2) rsbecker
2022-06-23 15:21 ` René Scharfe
2022-06-23 16:26   ` rsbecker
2022-06-23 16:27   ` 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=xmqqmte31h0x.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git-packagers@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=l.s.r@web.de \
    --cc=rsbecker@nexbridge.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.