From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: Uploading packages built against Perl 5.2.2 [
Date: Tue, 28 Jul 2015 17:31:00 -0000 [thread overview]
Message-ID: <55B7BC63.2050206@cornell.edu> (raw)
In-Reply-To: <20150728164013.GO7535@calimero.vinschen.de>
On 7/28/2015 12:40 PM, Corinna Vinschen wrote:
> On Jul 28 12:36, Ken Brown wrote:
>> On 7/28/2015 12:23 PM, Eric Blake wrote:
>>> On 07/28/2015 05:18 AM, Corinna Vinschen wrote:
>>>>>> One more thing that we'll have to solve one way or the other. I still
>>>>>> hope that one maintainer with full sourceware access will be able to
>>>>>> post the !ready cookies all at the same time.
>>>>>
>>>>> Corinna or Yaakov, that I am aware.
>>>>
>>>> Or Eric. I'm not sure how this !perl thingy is supposed to work since
>>>> the tags are handled by upset...
>>>>
>>>> As for setting bulk !ready tags, I can do that, but not this week. Next
>>>> Monday at the earliest.
>>>
>>> If it's just a matter of crawling all directories that have a !perl tag
>>> at the trigger point, and adding a !ready to those directories, that
>>
>> Not adding !ready, but renaming !perl to !ready.
>>
>>> seems simple enough to do. I think upset will just ignore !perl
>>
>> I just added !perl to my x86 and x86_64 directories. We'll see in a
>> half-hour or so how upset deals with it.
>
> Yay, experimenting on the life system. That's the spirit.
Thanks for the encouragement. In general I tend to be too cautious.
Anyway, upset seems to have come and gone. My !perl files are still there, and
I haven't seen any upset messages.
Ken
next prev parent reply other threads:[~2015-07-28 17:31 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 10:03 [ITA] Perl distributions (in preparation of Perl 5.22) Achim Gratz
2015-05-25 15:24 ` Achim Gratz
2015-05-29 19:26 ` Achim Gratz
2015-05-29 19:44 ` Yaakov Selkowitz
2015-05-29 19:46 ` Yaakov Selkowitz
2015-05-29 19:57 ` Achim Gratz
2015-05-29 20:43 ` Yaakov Selkowitz
2015-05-29 20:55 ` Achim Gratz
2015-05-29 19:50 ` Achim Gratz
2015-05-31 16:00 ` Marco Atzeri
2015-05-31 18:59 ` Achim Gratz
2015-06-22 16:59 ` Achim Gratz
2015-06-22 21:46 ` Marco Atzeri
2015-06-23 5:38 ` Achim Gratz
2015-07-02 21:13 ` Marco Atzeri
2015-07-03 5:36 ` Achim Gratz
2015-06-26 23:09 ` Yaakov Selkowitz
2015-06-30 3:05 ` Yaakov Selkowitz
2015-06-30 5:04 ` Achim Gratz
2015-07-04 10:46 ` Achim Gratz
2015-07-04 12:31 ` Marco Atzeri
2015-07-04 19:34 ` David Rothenberger
2015-07-05 6:02 ` Achim Gratz
2015-07-05 13:26 ` Ken Brown
2015-07-05 18:32 ` Yaakov Selkowitz
2015-07-05 19:44 ` Achim Gratz
2015-07-05 20:01 ` Ken Brown
2015-07-27 22:43 ` Uploading packages built against Perl 5.2.2 [Was: [ITA] Perl distributions (in preparation of Perl 5.22)] Adam Dinwoodie
2015-07-28 5:43 ` Uploading packages built against Perl 5.2.2 [ Achim Gratz
2015-07-28 6:40 ` Marco Atzeri
2015-07-28 11:18 ` Corinna Vinschen
2015-07-28 16:18 ` Achim Gratz
2015-07-28 16:36 ` Corinna Vinschen
2015-07-28 17:06 ` David Rothenberger
2015-07-28 17:20 ` Achim Gratz
2015-07-28 16:23 ` Eric Blake
2015-07-28 16:36 ` Ken Brown
2015-07-28 16:40 ` Corinna Vinschen
2015-07-28 17:31 ` Ken Brown [this message]
2015-07-28 16:37 ` Corinna Vinschen
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=55B7BC63.2050206@cornell.edu \
--to=kbrown@cornell.edu \
--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).