From: Libor Ukropec <ace@seznam.cz>
To: cygwin-apps@cygwin.com
Subject: Re: [ATTN MAINTAINER] tig
Date: Tue, 13 Dec 2022 18:14:53 +0100 [thread overview]
Message-ID: <83dddce7-1221-3fc5-2a5a-2d529b67da97@seznam.cz> (raw)
In-Reply-To: <20221212163241.6irqiecfn23hahvo@lucy.dinwoodie.org>
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 already
>> 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 cygport
>> file if it can save you some effort (in compare to the following scallywag,
>> 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ïve 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 for 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`) :)
next prev parent reply other threads:[~2022-12-13 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 22:15 Libor Ukropec
2022-12-12 16:32 ` Adam Dinwoodie
2022-12-13 17:14 ` Libor Ukropec [this message]
2022-12-13 18:32 ` Adam Dinwoodie
2022-12-13 22:05 ` Libor Ukropec
2023-01-10 14:04 ` Jari Aalto
2023-01-13 16:59 ` Libor Ukropec
2023-01-13 17:06 ` Libor Ukropec
2023-01-13 19:23 ` Brian Inglis
2023-01-13 19:40 ` Adam Dinwoodie
2023-01-16 12:42 ` Jon Turney
2023-01-25 11:41 ` Jari Aalto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83dddce7-1221-3fc5-2a5a-2d529b67da97@seznam.cz \
--to=ace@seznam.cz \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).