From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [Attn. Maintainers] Perl 5.26.1 (release is imminent)
Date: Mon, 23 Oct 2017 18:37:00 -0000 [thread overview]
Message-ID: <4bace447-7a0f-498a-4a22-b8da17edee1a@dronecode.org.uk> (raw)
In-Reply-To: <bacb54e6-fcd7-1c28-e1bc-465df98a7237@cornell.edu>
On 23/10/2017 19:03, Ken Brown wrote:
> On 10/23/2017 1:38 PM, Jon Turney wrote:
>> On 23/10/2017 18:17, Yaakov Selkowitz wrote:
>>> On 2017-10-18 17:15, David Rothenberger wrote:
>>>> On 10/18/2017 11:20 AM, Achim Gratz wrote:
>>>>> subversion-perl:Â Â Â Â A version control system (perl bindings)
>>>>
>>>> I've uploaded new subversion packages.
>>>
>>> Everything else is in place now, if you could take care of however you
>>> manage subversion normally; it didn't work for me, but I'm probably
>>> missing something.
>>
>> No, this is a calm problem. It (now) checks that curr: and prev: have
>> the chronological ordering one would naturally expect.
>>
>> Since subversion is special in that prev: is being used for 1.8, which
>> could be built before or after 1.9, I've added the subversion packages
>> to the list of exclusions for this rule.
>
> Did this somehow cause all maintainers to receive email about
> subversion? I just received a package upload report that contained what
> I expected about my own packages, but which also contained a report
> about subversion-1.9.5-2 being moved to the vault.
No, you're special :)
That was some other hiccup I'm investigating...
next prev parent reply other threads:[~2017-10-23 18:37 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 20:05 [Attn. Maintainers] Perl 5.26.1-RC1 Achim Gratz
2017-09-18 17:18 ` Ken Brown
2017-09-18 18:00 ` Achim Gratz
2017-09-18 20:00 ` Ken Brown
2017-09-25 21:21 ` Yaakov Selkowitz
2017-09-26 8:23 ` Ken Brown
2017-09-18 17:52 ` Achim Gratz
2017-09-19 6:11 ` Yaakov Selkowitz
2017-09-19 17:35 ` Achim Gratz
2017-09-24 9:09 ` Marco Atzeri
2017-09-24 9:25 ` Achim Gratz
2017-09-24 17:24 ` Marco Atzeri
2017-09-29 20:48 ` Marco Atzeri
2017-09-30 8:15 ` Achim Gratz
2017-09-24 15:59 ` [Attn. Maintainers] Perl 5.26.1 Achim Gratz
2017-09-24 17:16 ` Ken Brown
2017-09-24 17:22 ` Achim Gratz
2017-09-29 18:26 ` Jon Turney
2017-09-26 16:45 ` Achim Gratz
2017-09-29 18:06 ` Yaakov Selkowitz
2017-09-30 8:52 ` Achim Gratz
2017-09-30 15:25 ` Ken Brown
2017-10-02 20:39 ` Achim Gratz
2017-10-02 21:20 ` Ken Brown
2017-10-03 2:36 ` Brian Inglis
2017-10-03 6:35 ` Achim Gratz
2017-09-30 21:13 ` Marco Atzeri
2017-10-01 4:47 ` Marco Atzeri
2017-10-02 20:41 ` Achim Gratz
2017-09-30 22:49 ` Alexey Sokolov
2017-10-01 8:13 ` Achim Gratz
2017-10-09 16:41 ` Ken Brown
2017-09-26 16:50 ` Achim Gratz
2017-09-26 18:56 ` Achim Gratz
2017-09-26 20:42 ` Achim Gratz
2017-09-26 22:15 ` Yaakov Selkowitz
2017-09-27 4:51 ` Achim Gratz
2017-09-27 6:46 ` [Attn. Maintainers] Perl 5.26.1 (prepare for release) Achim Gratz
2017-09-30 20:30 ` Marco Atzeri
2017-10-04 17:24 ` Achim Gratz
2017-10-12 19:32 ` Achim Gratz
2017-10-12 20:34 ` Ken Brown
2017-10-13 18:02 ` Achim Gratz
2017-10-18 18:20 ` [Attn. Maintainers] Perl 5.26.1 (release is imminent) Achim Gratz
2017-10-18 20:21 ` Ken Brown
2017-10-18 22:16 ` David Rothenberger
2017-10-23 17:17 ` Yaakov Selkowitz
2017-10-23 17:38 ` Jon Turney
2017-10-23 18:03 ` Ken Brown
2017-10-23 18:37 ` Jon Turney [this message]
2017-10-19 6:04 ` Marco Atzeri
2017-10-19 15:00 ` Yaakov Selkowitz
2017-10-19 17:15 ` Achim Gratz
2017-10-23 17:47 ` Yaakov Selkowitz
2017-10-24 8:37 ` Adam Dinwoodie
2017-10-23 19:20 ` Achim Gratz
2017-10-24 16:22 ` Ken Brown
2017-10-24 18:45 ` Achim Gratz
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=4bace447-7a0f-498a-4a22-b8da17edee1a@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).