On Jun 13 16:54, Warren Young wrote:
Would someone flip this package from test to curr for me, please?
Leave 3.7.16.2-1 as prev.
Done. Do you want to keep 3.7.13-1?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer
On 6/14/2013 01:54, Corinna Vinschen wrote:
On Jun 13 16:54, Warren Young wrote:
Would someone flip this package from test to curr for me, please?
Leave 3.7.16.2-1 as prev.
Done.
Thanks!
Do you want to keep 3.7.13-1?
I didn't know I could have more than one prev.
Sure, let's keep it a
Would someone flip this package from test to curr for me, please?
Leave 3.7.16.2-1 as prev.
Il 6/10/2013 9:55 PM, Warren Young ha scritto:
Leave 3.7.16.2-1 as curr, and make this test only for now.
you should make it test adding the relevant
prev/current/test entries as specified on
http://cygwin.com/setup.html
(I am hoping to be able to promote it to curr later, but it changes
On 6/11/2013 01:37, marco atzeri wrote:
you should make it test adding the relevant
prev/current/test entries as specified on
http://cygwin.com/setup.html
Is there a way to set this via the .cygport file? I tried searching its
HTML manual, and didn't find one.
The alternative is to
On 6/11/2013 10:10 AM, Warren Young wrote:
On 6/11/2013 01:37, marco atzeri wrote:
you should make it test adding the relevant
prev/current/test entries as specified on
http://cygwin.com/setup.html
Is there a way to set this via the .cygport file? I tried searching its
HTML manual, and
Leave 3.7.16.2-1 as curr, and make this test only for now.
(I am hoping to be able to promote it to curr later, but it changes too
much to risk that without more testing. The only reason I'm RFU'ing it
is because there seems to be some resistance to installing test versions
from raw