From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi1-x22a.google.com (mail-oi1-x22a.google.com [IPv6:2607:f8b0:4864:20::22a]) by sourceware.org (Postfix) with ESMTPS id 6F634385222D for ; Tue, 13 Dec 2022 18:33:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 6F634385222D Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=dinwoodie.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=dinwoodie.org Received: by mail-oi1-x22a.google.com with SMTP id m204so615521oib.6 for ; Tue, 13 Dec 2022 10:33:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dinwoodie.org; s=google; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=GLiTZmedL1bvCPGPlRSanzkvFABfhyQuBtUE9J+7GqA=; b=pAPyh6GdVEwfsClFSPIb+TqK90uvudJ1h87NOxRnQ8o2S6OB5pmRFPUtgHedqgN5Ey 6f2N8leRi4rWK5H9l5HG5ha4s2NK6dLSloAeIt7jsyTuSkuW5rKZYMgFcx+R7ydWK/hM F9xBY79XJS8dLjmBfwJmYhnGePuk2GtGGYnsM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=GLiTZmedL1bvCPGPlRSanzkvFABfhyQuBtUE9J+7GqA=; b=D/anaceQ9Cu6tyoEZIQrTYkqMoZM50preR+tzC3mq9ui1iwM5ui2IHHJjfdYe9IuJ6 SoRV1roOSkC03sa9AdaUO0c4jVrW4c7WhLiwqvCXG8n5oxrK2ghUC1nAYpd2F/NY1tdM OqTZnjME0Vh8WcHKeVBnSgImsMrQV/Km5BBpnyA4Ehpi/Q80mmn2iknvJ/xYaFIwmu+3 XPntY5rylg23fs3e7gIvzeda5GGmJ3nJ7ZgPGsonZgN6xqHfghlDN6hdksFQQcsrXW5s NPa3bwrDDYkf9JArBKeCOGGoLemu5lKP7BQY0LJsR2zElj6CgchF86pFgkfLnqSJmwmb pPiA== X-Gm-Message-State: ANoB5plaPeJbRWyYpy5kp7MWSBvczUarg2Tj9llHOFb0bVNrSqoRahoS MRs7+4icV/HijmUaQUbX00N1tcv+mTDTodepPVuBHjTaOQ17Dw== X-Google-Smtp-Source: AA0mqf73eud5FDweK/NYyeYOsbPELcXwvTQ95T0aURkCWgEIH4xqzKJbFh/diH2bzBz1bTxvbOVoqtwOjEwzAsL0N8Q= X-Received: by 2002:a54:4885:0:b0:35a:8a2b:e901 with SMTP id r5-20020a544885000000b0035a8a2be901mr314754oic.249.1670956411894; Tue, 13 Dec 2022 10:33:31 -0800 (PST) MIME-Version: 1.0 References: <8db83a15-e595-7ffc-32b9-e7f9aa69e881@seznam.cz> <20221212163241.6irqiecfn23hahvo@lucy.dinwoodie.org> <83dddce7-1221-3fc5-2a5a-2d529b67da97@seznam.cz> In-Reply-To: <83dddce7-1221-3fc5-2a5a-2d529b67da97@seznam.cz> From: Adam Dinwoodie Date: Tue, 13 Dec 2022 18:32:55 +0000 Message-ID: Subject: Re: [ATTN MAINTAINER] tig To: cygwin-apps@cygwin.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=1.9 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,STOCK_QUOTE_BODY,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Tue, 13 Dec 2022 at 17:16, Libor Ukropec via Cygwin-apps wrote: > > Dne 12.12.2022 v 17:32 Adam Dinwoodie via Cygwin-apps napsal(a): > > On Sun, Dec 11, 2022 at 11:15:35PM +0100, Libor Ukropec via Cygwin-apps= wrote: > >> Hello Jari, > >> > >> cygwin contains "tig" in version 2.4.1 (2019-07-30) and there's alread= y > >> 2.5.4 (2021) with many bug fixes and improvements available. > >> Can I kindly ask whether it is possible to update the package? > >> I do not see a git repository for the tig package, so I attached the c= ygport > >> file if it can save you some effort (in compare to the following scall= ywag, > >> I've added the LICENSE info the script) > >> > >> Scallywag report is here: https://github.com/cygwin/scallywag/actions/= runs/3670966767 > > > > I believe Jari's repo for the tig Cygwin packaging is on GitHub[0], and > > it looks like it's using the old pre-Cygport packaging mechanism. I've > > not looked through that repo myself (yet, at least) but it looks like > > there are some patches that imply a na=C3=AFve build might not work > > perfectly. Or those packages might be entirely obsolete... > I did not look for the GitHub, but the naive compile and run worked with = few custom > actions in the cygport script. > > > > [0]: https://github.com/jaalto/cygwin-package--tig > > > > FWIW, I'd be happy to at least attempt to add this package to my small > > Cygwin Git packaging empire, and take responsibility for keeping it up > > to date going forwards. But that's only if Jari wants to relinquish > > Yes, let's wait for Jari's answer > > that hat, and even then I think Libor clearly gets first refusal given > > they've written the new Cygport file. > > > Here comes my weak English. Will I be refused by Jari or do you mean that= I will refuse > you because I did the Cygport file? > > If the latter, I have no objections you are the maintainer (let's wait fo= r Jari), I just > wanted to give a helpful hand, not only to rudely ask for the update. And= also to play > more with the cygports and expand my portfolio (I am shy to say `empire`)= :) Apologies for the idioms! I mean that if Jari wants to stop being the maintainer, you should be allowed to become the maintainer if you want to, because you wrote the up-to-date cygport file. "First refusal" means, essentially, that you get given the chance to do something before anyone else does. In this case, you'd get the option to become maintainer, and I would only get the option to do so if you refused.