git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Lars Schneider <larsxschneider@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>,
	"Git mailing list" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Mar 2018, #01; Thu, 1)
Date: Fri, 2 Mar 2018 18:39:39 +0100	[thread overview]
Message-ID: <3C32011B-30E5-4E63-8692-5D598430DC99@gmail.com> (raw)
In-Reply-To: <xmqqsh9icsh1.fsf@gitster-ct.c.googlers.com>


> On 02 Mar 2018, at 18:11, Junio C Hamano <gitster@pobox.com> wrote:
> 
> Junio C Hamano <gitster@pobox.com> writes:
> 
>> SZEDER Gábor <szeder.dev@gmail.com> writes:
>> 
>>> On Thu, Mar 1, 2018 at 11:20 PM, Junio C Hamano <gitster@pobox.com> wrote:
>>> 
>>>> * sg/travis-build-during-script-phase (2018-01-08) 1 commit
>>>> - travis-ci: build Git during the 'script' phase
>>>> 
>>>> Stalled for too long without any response; will discard.
>>> 
>>> I still think this is a good change as-is and it does make checking the
>>> results of Travis CI builds easier.  The issue Lars raised in [1] is in
>>> my opinion a non-issue [2] in practice and Lars hasn't yet disagreed
>>> with that.
>> 
>> OK, so I simply misread the discussion and did not realize that it
>> reached a conclusion?  If that's the case, good ;-).  Thanks.
> 
> OK, I think I now understand what happened.  I misread the "fold"
> discussion and thought we were still exploring the possibility, to
> avoid showing uninteresting zero-status case to the users.
> 
> If we do not care about that part, then it seems that the discussion
> thread is complete.  Let's move on.

All good with me. I just wanted explain my reasoning for the initial
implementation. I do understand Szeder's reasoning too and I am OK
with the change.

Thanks for improving the TravisCI integration Szeder!

- Lars

  reply	other threads:[~2018-03-02 17:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01 22:20 What's cooking in git.git (Mar 2018, #01; Thu, 1) Junio C Hamano
2018-03-02 10:23 ` Luke Diamand
2018-03-02 15:14 ` Derrick Stolee
2018-03-02 16:33 ` SZEDER Gábor
2018-03-02 17:07   ` Junio C Hamano
2018-03-02 17:11     ` Junio C Hamano
2018-03-02 17:39       ` Lars Schneider [this message]
2018-03-02 18:55       ` SZEDER Gábor

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=3C32011B-30E5-4E63-8692-5D598430DC99@gmail.com \
    --to=larsxschneider@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=szeder.dev@gmail.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).