On Tue, Apr 8, 2025 at 3:48 PM Jon Turney <jon.tur...@dronecode.org.uk> wrote:
>
> In future, if you could please attach patches to emails, that makes them
> easier to use.
Of course. When in doubt, I follow LKML's long established practice.
Good to know mime type attachments supported here!
A few questions that came up along the way:
1. Do you sign git commits (-S, --gpg-sign) or advise to do so?
2. This package has no reverse dependencies, is not too complicated,
so I guess it's a case for straight to "stable" without the need for
testing probation period. What are the criteria for a package to be
deployed initially as "test"? I'm guessing
compilers/interpreters/toolchain/anything heavily patched.
3. Treecleaning. There were 3 older versions of the package nano
present. Is it the responsibility of the maintainer to tidy up? (If
so, how?) Unless there is a business case for older versions, and if
no hate mail arrived some time after the latest update (weeks,
months), I guess it's safe to purge.
- Actually, I see that
https://cygwin.com/package-upload.html#deleting seems to handle some
of that. I see it took out the oldest, 2.9.7 (`calm` emailed me so),
but 4.3 and 4.9 remain there for now.
4. Is there an easy way to download the whole tree of *.cygport files?
I'm only looking for a snapshot of the files if possible, not the
totality of git repos. That would help to "check/consult/figure out
something", instead of using web browser, very slowly.
Regards,
Philippe Baril Lecavalier
