From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Christian Couder <christian.couder@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git-for-windows@googlegroups.com, git <git@vger.kernel.org>
Subject: Re: [git-for-windows] Re: Continuous Testing of Git on Windows
Date: Wed, 15 Feb 2017 15:07:06 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1702151506250.3496@virtualbox> (raw)
In-Reply-To: <CAP8UFD1+AgBVqSh=wHteM3uKO+55ZqqD4cHzBUfN0KTPXyvutQ@mail.gmail.com>
Hi Christian,
On Wed, 15 Feb 2017, Christian Couder wrote:
> On Tue, Feb 14, 2017 at 10:08 PM, Junio C Hamano <gitster@pobox.com>
> wrote:
>
> > Probably a less resource intensive approach is to find the tips of the
> > topics not in 'next' but in 'pu' and test them. That would give you
> > which topic(s) are problematic, which is a better starting point than
> > "Oh, 'pu' does not build". After identifying which branch is
> > problematic, bisection of individual topic would be of more manageable
> > size.
>
> It is still probably more resource intensive than it couls be.
Indeed.
Ciao,
Dscho
prev parent reply other threads:[~2017-02-15 14:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 12:24 Continuous Testing of Git on Windows Johannes Schindelin
2017-02-13 23:46 ` Junio C Hamano
2017-02-14 20:55 ` [git-for-windows] " Johannes Schindelin
2017-02-14 21:08 ` Junio C Hamano
2017-02-14 23:00 ` Christian Couder
2017-02-14 23:11 ` Junio C Hamano
2017-02-14 23:27 ` Philip Oakley
2017-02-14 23:35 ` Junio C Hamano
2017-02-15 17:31 ` Philip Oakley
2017-02-15 21:26 ` Junio C Hamano
2017-02-15 23:33 ` Philip Oakley
2017-02-16 1:33 ` Junio C Hamano
2017-02-15 22:19 ` Philip Oakley
2017-02-15 22:19 ` Philip Oakley
2017-02-15 14:22 ` Johannes Schindelin
2017-02-15 23:57 ` Philip Oakley
2017-02-16 0:20 ` Junio C Hamano
2017-02-18 11:49 ` Philip Oakley
2017-02-15 14:07 ` Johannes Schindelin [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=alpine.DEB.2.20.1702151506250.3496@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=git-for-windows@googlegroups.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.
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 NNTP newsgroup(s).