Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fSToG-0002Rc-6F for pgsql-hackers@arkaria.postgresql.org; Mon, 11 Jun 2018 20:53:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fSToE-0001MM-Mq for pgsql-hackers@arkaria.postgresql.org; Mon, 11 Jun 2018 20:53:02 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fSToD-0001DE-Jb for pgsql-hackers@lists.postgresql.org; Mon, 11 Jun 2018 20:53:02 +0000 Received: from homie-sub4.mail.dreamhost.com ([69.163.253.135] helo=homiemail-a102.g.dreamhost.com) by magus.postgresql.org with esmtps (TLS1.1:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fSTo6-0005eq-60 for pgsql-hackers@postgresql.org; Mon, 11 Jun 2018 20:53:00 +0000 Received: from homiemail-a102.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a102.g.dreamhost.com (Postfix) with ESMTP id EA19B2004E509; Mon, 11 Jun 2018 13:52:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=1d1HEA+RLMPJiZ lsjTIysCO9Yl8=; b=pwk6qgHEo7ZxIs9UJuTpa9yqutbaL31wbF2DYvejl9mSNu Xn3HNkp0FtXPwkg+SxU7wq2ga6x91mpsH1uaoMLV9vHzUfuBY8siV+0hXMXR5GlF /UR9+s787lXIyJtM2b/iCaKZCwLQuwNJahK4qjsylN1zQy6fnFwohnEsEmyOg= Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a102.g.dreamhost.com (Postfix) with ESMTPSA id 89C792004E505; Mon, 11 Jun 2018 13:52:48 -0700 (PDT) Date: Mon, 11 Jun 2018 15:52:46 -0500 From: Nico Williams To: Andrew Dunstan Cc: Robert Haas , Thomas Munro , PostgreSQL mailing lists Subject: Re: [PATCH v16] GSSAPI encryption support Message-ID: <20180611205245.GB23356@localhost> References: <20180607210058.GE24501@localhost> <20180611171315.GA23356@localhost> <10fecbaa-24d0-cd86-952d-92827929a85c@2ndQuadrant.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10fecbaa-24d0-cd86-952d-92827929a85c@2ndQuadrant.com> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, Jun 11, 2018 at 01:31:12PM -0400, Andrew Dunstan wrote: > On 06/11/2018 01:13 PM, Nico Williams wrote: > >Well, all the free CIs like Travis and Appveyor do it this way. You > >don't have to *use* it just because the .yml files are in the source > >tree. But you have to have the .yml files in the source tree in order > >to use these CIs. It'd be nice to be able to point somewhere else for > >them, but whatever, that's not something we get much choice in at this > >time. > > That's not true, at least for Appveyor (can't speak about travis - I have no > first hand experience). For appveyor, you can supply a custom appveyor.yml > file, which can be a complete URL. In fact, if you use a plain git source as > opposed to one of the managed git services it supports, you have to do it > that way - it ignores an appveyor.yml in your repo. I found this out the > very hard way over the last few days, and they very kindly don't warn you at > all about this. OK, that's.. nice, maybe, I guess, but I'd still want version control for these yml files -- why not have them in-tree? I'd rather have them in-tree unless there's a good reason not to have them there. In other projects I definitely find it better to have these files in-tree. Nico --