From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
Mark Geisert <mark@maxrnd.com>
Subject: Re: [NMU] inkscape 0.92.3-2 (Test)
Date: Sun, 3 Dec 2023 15:33:47 +0000 [thread overview]
Message-ID: <f99be8b2-c4d8-4287-a41b-c2ad13899f46@dronecode.org.uk> (raw)
In-Reply-To: <30c5f6fa-71ea-0854-809d-6644f287d322@maxrnd.com>
On 01/12/2023 09:17, Mark Geisert via Cygwin-apps wrote:
>
>> If you have ideas about how to make things work better, I'm all ears.
>>
>> For the moment, I tweaked things to let your upload through.
>
> Thanks Jon. I have only seen a handful of NMUs go by and it didn't
> occur to me that those doing them were explicitly allowed to.
>
> ISTM the process works fine as it is. If I happen to have a future itch
> to do an NMU should I handle it as I did this one? Or say something on
> cygwin-apps beforehand? I don't expect it will be often. I'm totally
> fine not being on the "trusted" list for this type of thing.
If you ask in advance, that's possibly slightly less work for me, but
either is fine really.
Maybe I should make things so that all maintainers can NMU orphaned
packages. That seems reasonable I guess?
> Thanks,
No problem.
next prev parent reply other threads:[~2023-12-03 15:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 0:38 Mark Geisert
2023-11-30 13:45 ` Jon Turney
2023-12-01 9:17 ` Mark Geisert
2023-12-03 15:33 ` Jon Turney [this message]
2023-12-03 17:50 ` Brian Inglis
2023-12-05 13:07 ` Jon Turney
2023-12-06 17:19 ` Brian Inglis
2023-12-06 17:30 ` Brian Inglis
2023-12-20 12:16 ` Unmaintained packages in base package set Jon Turney
2023-12-21 4:27 ` Marco Atzeri
2023-12-22 2:06 ` Mark Geisert
2023-12-22 16:37 ` Jon Turney
2023-12-23 3:42 ` Takashi Yano
2023-12-23 3:51 ` Marco Atzeri
2024-01-03 4:59 ` Takashi Yano
2024-01-03 7:49 ` Marco Atzeri
2024-01-07 12:54 ` Jon Turney
2024-01-07 13:35 ` Takashi Yano
2024-01-07 15:14 ` Takashi Yano
2024-01-07 15:44 ` ASSI
2024-01-26 5:03 ` Marco Atzeri
2024-01-03 15:39 ` 1dakotaxi
2023-12-11 19:21 ` [NMU] inkscape 0.92.3-2 (Test) ASSI
2023-12-14 6:57 ` Mark Geisert
2023-12-23 0:37 ` Mark Geisert
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=f99be8b2-c4d8-4287-a41b-c2ad13899f46@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=mark@maxrnd.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).