From owner-freebsd-git@freebsd.org Thu Jul 2 14:08:29 2020 Return-Path: Delivered-To: freebsd-git@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 18CA535707D for ; Thu, 2 Jul 2020 14:08:29 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f49.google.com (mail-io1-f49.google.com [209.85.166.49]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49yKgv4njbz3cl6 for ; Thu, 2 Jul 2020 14:08:27 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io1-f49.google.com with SMTP id y2so29012818ioy.3 for ; Thu, 02 Jul 2020 07:08:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Yp4GVI8StwkXvVa1AkV96V6BQnhGCzjm21dN2KGajY0=; b=KcnZC82GcjzTFc5HSZDsAx3b2qkmUKt/iEtpYleJLtEmEcfV7ufzcE2Mkj6cV7Mo02 Xg09scMKoaXnFoheee5hugQiLT9tpXUuqs7Zmc/nNgz9wUVH5bmhr1zlanJET1BoVDdd RSoYdZ2cr1/0VvSsBSarK1FPSaNJVfTGw+TbrC3foHuK8r2AQlhNiVK7NmTDJyRDrXpR mJw+UAqRZYtgwdmbtSNfurBu2rC5noNWJd6ohkeb0sdsNXwalyFCXcFpZn1DaFkBhOVM 1XC7kHwpVSqK5gM4DSUg8khPhvTIydzPzuu5CKblzuKhuJ7kEptdcjflpawk/LdfOE8D Zy3Q== X-Gm-Message-State: AOAM533pulNxft6dpz8szt/avUtiOuWxAf/9S9R2iwPfsZeOLqc3zJK/ jPeIGhbE2Rn50+yaWQuaBAWrVoeNBLsEDawfWNgENP4x X-Google-Smtp-Source: ABdhPJyutRqKMiE/dwCDOJbD3qcp/Yg81ykfF8udIABCq7TK60oUtG7R/6Fl3Y3LEsRohfzURv7REHmd2Jqwp4mJL7M= X-Received: by 2002:a5d:9c44:: with SMTP id 4mr7665110iof.15.1593698906456; Thu, 02 Jul 2020 07:08:26 -0700 (PDT) MIME-Version: 1.0 References: <30741857-E21A-4EB9-9C01-81D1E8B8AC03@langille.org> In-Reply-To: <30741857-E21A-4EB9-9C01-81D1E8B8AC03@langille.org> From: Ed Maste Date: Thu, 2 Jul 2020 10:08:14 -0400 Message-ID: Subject: Re: discovering new commits: FreshPorts To: Dan Langille Cc: freebsd-git@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 49yKgv4njbz3cl6 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.49 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-1.96 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.89)[-0.892]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; NEURAL_HAM_LONG(-0.97)[-0.965]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-git@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.10)[-0.104]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[209.85.166.49:from]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.166.49:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-git@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussion of git use in the FreeBSD project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jul 2020 14:08:29 -0000 On Wed, 1 Jul 2020 at 17:51, Dan Langille wrote: > > The biggest remaining issue: what method should FreshPorts use to start working on a new commit? What process replaces the incoming svn commit email? > > At present, there is no email for the git commits (re https://lists.freebsd.org/mailman/listinfo). It's only the svn commits. We will have a git commit mailing list by the time we're ready to make the switch, but indeed it's not there yet. > I see these choices: > > 1- continue to process based upon incoming email, but use that only as the reason to wake up and check git for new commits. > > I don't know how commits arriving in svn relate to commits arriving in git - will they be there? There's usually 0-15 minutes of latency between a commit to svn and the same change appearing in the (GitHub) git mirror, but sometimes it's a bit longer. This might work some of the time but isn't going to be reliable. > 2 - repeatedly run 'git fetch origin' to check for new commits > > We won't miss a thing - but that's rather DDosS-ish. As long as the polling frequency is not too high this should be fine. > 3 - a commit hook. > > The git repo hits up a FreshPorts url on each commit. This sounds like the best approach, and I'd be happy for us to add this to the new git repo config.