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 1fSQf1-0003Fc-QK for pgsql-hackers@arkaria.postgresql.org; Mon, 11 Jun 2018 17:31:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fSQf0-0002vE-MG for pgsql-hackers@arkaria.postgresql.org; Mon, 11 Jun 2018 17:31:18 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fSQf0-0002u8-BS for pgsql-hackers@lists.postgresql.org; Mon, 11 Jun 2018 17:31:18 +0000 Received: from mail-yw0-x241.google.com ([2607:f8b0:4002:c05::241]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fSQex-0007TK-F6 for pgsql-hackers@postgresql.org; Mon, 11 Jun 2018 17:31:17 +0000 Received: by mail-yw0-x241.google.com with SMTP id v197-v6so6576696ywc.13 for ; Mon, 11 Jun 2018 10:31:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=from:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=pofhpAejddWHR+KfT08c+UeC7DDPerq1ly9zltcai/g=; b=l+LxdPYM8Rq7LHc8POpU5CP2gIHSYcCrUGh1ax70X8evwsFVUuNEJfVrD2HkoaUdSj 1bSig8C1pFNSw2RMBiIkaBjLpvtoQYy+mmd3q/mXtA2Ro7DyOwt0HYWogj8tYt888Yhg 6/WRQZSxp7shR85jCD/B2YRNUQaxgfiWJ9RH0PTVGou0vehjt0zDVaPvPdKwTh4ZzI5M Seekg5l7b0rXaJ093fd6FflcUUcoEwMvqSQ4DV+mx/lXxf6q+dSPQ4U7uoA7aTxCWTpc p6wMG62m0pzU22Jc72yOEYv4MxG629dpIID11Q2RmJra+/xhbnvrlP738bfkWTfr6jRz 6zxw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=pofhpAejddWHR+KfT08c+UeC7DDPerq1ly9zltcai/g=; b=DCfa8Kk/Y5SjN+wjQ7ZyUiGNFKfNVK7NxTfIYEyHGFTaLHRC5M5anBh2HgZqfr/0Uj l+58/E7Pa51eepPSVGdrGknfqBYNi8mkAj62qESOgAhNZQgrHmP4s0yVQdZpom+BlXms H94DJWFCfjVtmZDtBzDBtaHDmv4heuFsysQHD8INgR7ID14H1XVdwJrONSr7gwfKj0Up epxJe36gc4vXO2JTDurrwmuM6JRIAuMSjUgaWTVb0FuQ0QVk7FuhqYJB0f7zXc1mYuqE 5KNcBRnxwLsNLYfpBh+oI98FBMa9wsyGZS+mM6P7qP/r+TYS38ogN82Q52cBn0Q9Q7Jo Tw5A== X-Gm-Message-State: APt69E1QdENnYcyo997nrNw7V/vbtFMJ6AiPrfI32nLl6jGaNMfJf9U+ zq0O9J8xnYAIiNdCLOCocIBm X-Google-Smtp-Source: ADUXVKJr4Uy2pgbCA9mml7ZMrGONtK9t7WnkjGG6NyymwaxfcyrruWjh6ymn3B+klbbYvh/RiswB+w== X-Received: by 2002:a81:a108:: with SMTP id y8-v6mr77813ywg.234.1528738274321; Mon, 11 Jun 2018 10:31:14 -0700 (PDT) Received: from [192.168.10.146] ([98.122.175.38]) by smtp.gmail.com with ESMTPSA id d22-v6sm30363406ywh.27.2018.06.11.10.31.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Jun 2018 10:31:13 -0700 (PDT) From: Andrew Dunstan X-Google-Original-From: Andrew Dunstan Subject: Re: [PATCH v16] GSSAPI encryption support To: Nico Williams , Robert Haas Cc: Thomas Munro , Robbie Harwood , PostgreSQL mailing lists , Michael Paquier , Stephen Frost References: <20180607210058.GE24501@localhost> <20180611171315.GA23356@localhost> Message-ID: <10fecbaa-24d0-cd86-952d-92827929a85c@2ndQuadrant.com> Date: Mon, 11 Jun 2018 13:31:12 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20180611171315.GA23356@localhost> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-MW List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services