All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Dennis Kaarsemaker <dennis@kaarsemaker.net>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
	Roberto Tyley <roberto.tyley@gmail.com>,
	Jeff King <peff@peff.net>, Luke Diamand <luke@diamand.org>,
	Johannes Schindelin <johannes.schindelin@gmx.de>,
	Lars Schneider <larsxschneider@gmail.com>,
	Git Users <git@vger.kernel.org>
Subject: Re: [RFC/PATCH v1] Add Travis CI support
Date: Mon, 05 Oct 2015 09:51:50 -0700	[thread overview]
Message-ID: <xmqqpp0tz2ah.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1443981968.3520.5.camel@kaarsemaker.net> (Dennis Kaarsemaker's message of "Sun, 04 Oct 2015 20:06:08 +0200")

Dennis Kaarsemaker <dennis@kaarsemaker.net> writes:

> On zo, 2015-10-04 at 10:46 -0700, Junio C Hamano wrote:
>> One final question.  Which configuration file does the CI use when
>> running a PR-initiated test?  The one already in the repository
>> i.e. the target of the proposed pull, or the one that is possibly
>> updated by the PR?
>>
>> I am wondering if that can be an avenue for a possible mischief.
>
> The latter. And it can, as it can enable notifications.

So it can add a slight annoyance if somebody wanted to, but not much
over the annoyance a random pull-request can already give to project
participants.  IOW, nothing to worry about.

Thanks.

  parent reply	other threads:[~2015-10-05 16:51 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 21:43 [RFC/PATCH v1] Add Travis CI support larsxschneider
2015-09-24 21:43 ` larsxschneider
2015-09-25  0:41 ` Junio C Hamano
2015-09-25  3:14   ` Dennis Kaarsemaker
2015-09-25  7:27     ` Johannes Schindelin
2015-09-25  8:05       ` Luke Diamand
2015-09-25 17:41         ` Junio C Hamano
2015-09-26 16:40         ` Lars Schneider
2015-09-27 12:11         ` Matthieu Moy
2015-09-28 17:21           ` Stefan Beller
2015-09-28 17:37           ` Matthieu Moy
2015-09-28 18:47             ` Junio C Hamano
2015-09-28 19:07               ` Matthieu Moy
2015-10-03 22:23               ` Roberto Tyley
2015-10-04  1:27                 ` Junio C Hamano
2015-10-04  1:37                   ` Junio C Hamano
2015-10-04  8:13                     ` Dennis Kaarsemaker
2015-10-04 12:51                     ` Johannes Schindelin
2015-10-04  7:59                   ` Matthieu Moy
2015-10-04 17:46                     ` Junio C Hamano
2015-10-04 18:06                       ` Dennis Kaarsemaker
2015-10-05  6:54                         ` Matthieu Moy
2015-10-05 16:51                         ` Junio C Hamano [this message]
2015-10-12  8:03                       ` Sebastian Schuberth
2015-10-04 17:59                     ` Junio C Hamano
2015-10-04  3:34                 ` Jeff King
2015-10-02 16:40     ` Sebastian Schuberth
2015-09-25 16:26   ` Jeff King
2015-09-25 18:29     ` Junio C Hamano
2015-09-25 18:52       ` Jeff King
2015-09-26 21:54         ` Shawn Pearce

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=xmqqpp0tz2ah.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=dennis@kaarsemaker.net \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    --cc=larsxschneider@gmail.com \
    --cc=luke@diamand.org \
    --cc=peff@peff.net \
    --cc=roberto.tyley@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.