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

Re: [PATCH v2] travis-ci: fix Perforce install on macOS

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 23, 2017, 18:39 UTC
Message-ID
<xmqqmvehsjrv.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20170122225550.28422-1-larsxschneider@gmail.com>
Lars Schneider <larsxschneider@gmail.com> writes:
Show 23 quoted lines
> The `perforce` and `perforce-server` package were moved from brew [1][2]
> to cask [3]. Teach TravisCI the new location.
>
> Perforce updates their binaries without version bumps. That made the
> brew install (legitimately!) fail due to checksum mismatches. The
> workaround is not necessary anymore as Cask [4] allows to disable the
> checksum test for individual formulas.
>
> [1] https://github.com/Homebrew/homebrew-binary/commit/1394e42de04d07445f82f9512627e864ff4ca4c6
> [2] https://github.com/Homebrew/homebrew-binary/commit/f8da22d6b8dbcfcfdb2dfa9ac1a5e5d8e05aac2b
> [3] https://github.com/caskroom/homebrew-cask/pull/29180
> [4] https://caskroom.github.io/
>
> Signed-off-by: Lars Schneider <larsxschneider@gmail.com>
> ---
>
> Hi,
>
> this small update removes one more unnecessary line and makes the
> formula name lower case (no functional reason - just looks better ;-).
>
> @Junio: Do you prefer such a v2 as "--in-reply-to" to v1 or as separate
>         thread? What eases your workflow?

It does not make that much of a difference if the second one comes within a few days since the first one but in general it probably would help if the follow-up is threaded _and_ made it clear upfront that if somebody is reading v2 then v1 can be ignored ;-).

Thanks.
Previous: Lars Schneider
Message 2 of 2 in “travis-ci: fix Perforce install on macOS”
  1. travis-ci: fix Perforce install on macOSLars Schneider, Jan 22, 2017
  2. Junio C HamanoJan 23, 2017

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.