From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) by sourceware.org (Postfix) with ESMTPS id 5F19E3858402 for ; Fri, 17 Dec 2021 02:46:54 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 5F19E3858402 Received: by mail-wr1-x42b.google.com with SMTP id o13so1310286wrs.12 for ; Thu, 16 Dec 2021 18:46:54 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=qrXGqxH5IaFwXsxR6I/A/AMBfqjMyVGcd4aCceo5SCQ=; b=aSyV8PyB/Zz+PEDhAMYShXm9H95t1KH/WrFpNkMyE6js+HOXTSW2KsJTA8KKPJRCdL 8PXiP5RZy6ew4OR846n+XVYge5RxzMAFTWDAaSa+dscIdRSqL9UooY2gJrvyWwiUGwFf cA0Bw8AgHZ1VXeOLL9x2BwC4+1iVI5kO4m0NDFZ0AFoKE4bvKIL1A4/ge6YxjfnwspqZ vei8/A76q6FGzEt8Wq0sql8G7Ug1uc3nnVJi+GYrW/1U+STLC5pE5GaIbUVNCgmPUAi6 W4mmkXORkuAGiJIuyL7+Nq1ayXu/WDc346rGRj98puiEUQ8eFx+oeQmBvAZbqstBwxAG VYNA== X-Gm-Message-State: AOAM531SQ2p/DxmWl9LNrh6TI1dBv3AWIqXHMm5SsBZ41T2OFpXaLm/z m30uIKJ99fywnagt/K51e28For6USVTn X-Google-Smtp-Source: ABdhPJyF9CUEEj+vB9epaiEhmrD0cGejJ+NVIKmLoJx+2xc8os0VlcFgeLQelfuVZGOE4ZbgRj7yaw== X-Received: by 2002:a05:6000:18a7:: with SMTP id b7mr644498wri.308.1639709213436; Thu, 16 Dec 2021 18:46:53 -0800 (PST) Received: from takamaka.home (lfbn-reu-1-492-16.w92-130.abo.wanadoo.fr. [92.130.80.16]) by smtp.gmail.com with ESMTPSA id h4sm6267736wrf.93.2021.12.16.18.46.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 16 Dec 2021 18:46:53 -0800 (PST) Received: by takamaka.home (Postfix, from userid 1000) id 83DA9A49F7; Fri, 17 Dec 2021 06:46:50 +0400 (+04) Date: Fri, 17 Dec 2021 06:46:50 +0400 From: Joel Brobecker To: overseers@sourceware.org Cc: Joel Brobecker Subject: Re: transition git-hooks on sourceware.org to Python 3.x Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Dec 2021 02:46:56 -0000 Hello, > I've created a small prototype and did some testing with it, > it seems to work well. In a nutshell, we have: > > / > - hooks/ <-- directory to use as hooks in Git bare repos > - git-hooks/ <-- clone of https://github.com/adacore/git-hooks > - python3-for-git-hooks/ <-- Python 3.x venv to be used by the git-hooks > > To transition a repository to updated hooks, we simply replace > the hooks symbolic link to point to /hooks. > > My proptotype is at... > > /home/gdbadmin/brobecke/py3-git-hooks/git-hooks-wrapper > > ... for those who are curious and can log onto sourceware.org. > There is a README.md file that gives a bit more information > (I'll attach to this message as well) > > If agreed with the approach, I think we'll want to decide where > we want this to live. Maybe /sourceware/projects/src-home/? If there are no opinions, I'll use gdbadmin's home. I don't think this is the ideal location, but that's one where I currently have access to. > The main issue with this location is that I worry about shared > access and in particular maintenance over time. I'd like to be > able to make changes there if there is a need to fix something. > I'd like also to be able to continue updating the git-hooks version > being used as I continue to push fixes and enhancements. Thank you, -- Joel