From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Lars Schneider <larsxschneider@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: [PATCH v1] travis-ci: build and test Git on Windows
Date: Thu, 23 Mar 2017 16:41:14 -0400 [thread overview]
Message-ID: <20170323204114.ui7jqrd3guwc3sgl@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqq7f3fbury.fsf@gitster.mtv.corp.google.com>
On Thu, Mar 23, 2017 at 01:30:41PM -0700, Junio C Hamano wrote:
> >> We can blacklist these branches with a regex in the travis.yml:
> >> https://docs.travis-ci.com/user/customizing-the-build#Building-Specific-Branches
> >
> > I had a feeling it might be something like that. So we would all need to
> > agree on the convention for WIP branch names. If other people like the
> > idea, I'm happy to make a patch, but I don't want to impose my own weird
> > conventions on everyone else.
>
> I can go with any convention, but I'd be more pleased if you made
> sure that "do not build this with CI" and "this is WIP" are kept as
> two separate concepts, as I can see having some WIP that I do want
> to get tested.
>
> Perhaps a substring "/noci-" anywhere in the branch name, or
> something silly like that?
Hrm, most of the point for me was _not_ having to define the two
concepts separately. Let me try it for a while with "[ci skip]" in the
tip commit subject, and see how painful I find that. My goal is
eventually to turn on notifications, so I'd quickly be reminded if I
forgot such a marker.
-Peff
next prev parent reply other threads:[~2017-03-23 20:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 6:56 [PATCH v1] travis-ci: build and test Git on Windows Lars Schneider
2017-03-22 15:49 ` Johannes Schindelin
2017-03-23 18:19 ` Lars Schneider
2017-03-22 19:29 ` Junio C Hamano
2017-03-23 16:22 ` Johannes Schindelin
2017-03-23 18:01 ` Jeff King
2017-03-23 19:12 ` Junio C Hamano
2017-03-23 19:17 ` Jeff King
2017-03-23 19:26 ` Lars Schneider
2017-03-23 19:30 ` Junio C Hamano
2017-03-23 19:36 ` Lars Schneider
2017-03-23 20:10 ` Junio C Hamano
2017-03-23 19:38 ` Jeff King
2017-03-23 20:00 ` Lars Schneider
2017-03-23 20:20 ` Jeff King
2017-03-23 20:30 ` Junio C Hamano
2017-03-23 20:41 ` Jeff King [this message]
2017-03-23 20:39 ` Lars Schneider
2017-03-23 20:42 ` Jeff King
2017-03-24 23:50 ` Johannes Schindelin
2017-03-23 21:04 ` Samuel Lijin
2017-03-23 19:15 ` Junio C Hamano
2017-03-23 18:23 ` Lars Schneider
2017-03-23 20:16 ` 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=20170323204114.ui7jqrd3guwc3sgl@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsxschneider@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).