Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)

From: Lars Schneider <larsxschneider@gmail.com>
Date: Sep 15, 2017, 07:50 UTC
Message-ID: <44574AF3-D215-4486-B7AE-72F83CC934C5@gmail.com>
In-Reply-To: <xmqq8thgy03t.fsf@gitster.mtv.corp.google.com>

On 15 Sep 2017, at 07:58, Junio C Hamano <gitster@pobox.com> wrote:

> Here are the topics that have been cooking.  Commits prefixed with
> '-' are only in 'pu' (proposed updates) while commits prefixed with
> '+' are in 'next'.  The ones marked with '.' do not appear in any of
> the integration branches, but I am still holding onto them.

> ...

Show 11 quoted lines

> * ls/travis-scriptify (2017-09-11) 3 commits
>  (merged to 'next' on 2017-09-14 at 8fa685d3b7)
> + travis: dedent a few scripts that are indented overly deeply
> + travis-ci: skip a branch build if equal tag is present
> + travis-ci: move Travis CI code into dedicated scripts
> 
> The scripts to drive TravisCI has been reorganized and then an
> optimization to avoid spending cycles on a branch whose tip is
> tagged has been implemented.
> 
> Will merge to 'master'.

SZEDER noticing a bug in this series that I was about to fix: https://public-inbox.org/git/3B175D35-5B1C-43CD-A7E9-85693335B10A@gmail.com/

I assume at this point a new patch is better than a re-roll, right?

Thanks, Lars