From: Eric Sunshine <sunshine@sunshineco.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH] ci/install-depends: attempt to fix "brew cask" stuff
Date: Fri, 15 Jan 2021 01:05:31 -0500 [thread overview]
Message-ID: <CAPig+cTSbwURNUEoUk8UCtVM69NuWg545zavJkyCYw8T6aG1SQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqa6tavjgm.fsf@gitster.c.googlers.com>
On Fri, Jan 15, 2021 at 12:50 AM Junio C Hamano <gitster@pobox.com> wrote:
> Junio C Hamano <gitster@pobox.com> writes:
> > It seems that homebrew suddenly started giving us trouble, like this:
> > https://github.com/git/git/runs/1705953982?check_suite_focus=true#step:3:70
> >
> After seeing 'seen' with this patch at its tip pass the tests [*1*],
> I prepared a merge of this change into the tip of 'next' and
> tentatively updated 'seen' with it.
>
> The test is still running [*2*], but the problematic part in the
> macOS build has already passed, so I am planning to fast-track this
> change down to 'next', 'master' and eventually down to 'maint' to
> keep the CI going to help other platforms catch more interesting
> problems.
>
> Help from those who are more familiar with macOS and homebrew is
> still appreciated, though.
I looked over your Homebrew-related changes, and they seem fine.
The `brew install homebrew/cask/perforce` command could be shortened
to `brew install perforce`, at least at the present, but being
explicit with the long identifier is probably better anyhow.
next prev parent reply other threads:[~2021-01-15 6:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 3:14 [PATCH] ci/install-depends: attempt to fix "brew cask" stuff Junio C Hamano
2021-01-15 5:48 ` Junio C Hamano
2021-01-15 6:05 ` Eric Sunshine [this message]
2021-01-15 14:27 ` Derrick Stolee
2021-01-15 19:52 ` Junio C Hamano
2021-01-15 19:59 ` Jeff King
2021-01-15 20:07 ` Eric Sunshine
2021-01-15 20:46 ` Jeff King
2021-02-01 22:11 ` SZEDER Gábor
2021-01-24 2:41 ` Philippe Blain
2021-01-24 6:18 ` Junio C Hamano
2021-01-25 0:56 ` Taylor Blau
2021-01-27 22:21 ` Jeff King
2021-01-28 5:23 ` 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPig+cTSbwURNUEoUk8UCtVM69NuWg545zavJkyCYw8T6aG1SQ@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).