From: Michael Gundlach <adblockforchrome@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cygwin 1.7.15: svn disk I/O error
Date: Tue, 07 Aug 2012 12:16:00 -0000 [thread overview]
Message-ID: <CABVhxxKA9oDn8KEwgVjpxL2Qke+TzpjteoJRFuiXHk13URV64A@mail.gmail.com> (raw)
In-Reply-To: <50207BAC.7030306@etr-usa.com>
On Mon, Aug 6, 2012 at 10:21 PM, Warren Young <warren@etr-usa.com> wrote:
>>> What reason could there be for a new Cygwin DLL to be accompanied by a
>>> new
>>> version of SQLite? Their maintainerships are entirely decoupled.
>>
>> Pardon my ignorance; I'm not familiar with the release process.
>
> Well, to a first approximation, it's entirely asynchronous. Every package
> maintainer releases versions on whatever schedule they wish. There are
> probably dozens of active Cygwin package maintainers.
Got it; I had somehow gotten the impression that there was one big
synchronized release-to-production of the Cygwin binary and all
packages.
> You have to enter the Cygwin Time Machine to do that:
> http://www.fruitbat.org/Cygwin/index.html#cygwincirca
Thanks!
> Bottom line: it's going to take at least a few days if you want to wait,
> maybe a week, maybe more. If you have to have a fix today, use the Time
> Machine.
Thanks for the insight into the package release process. Given that
branch reintegration is so dicey that I've ended up doing
while [ 1 ]; do
cleanup && revert && reintegrate && break;
done
, I think I'll use the Time Machine :)
Michael
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-08-07 12:01 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABVhxxKw8i96668GgHmMyPXCn+nBS8S874Q7wSSHgoer8iiSsw@mail.gmail.com>
2012-08-07 1:10 ` Michael Gundlach
2012-08-07 1:55 ` Warren Young
2012-08-07 1:57 ` Michael Gundlach
2012-08-07 2:42 ` Warren Young
2012-08-07 12:16 ` Michael Gundlach [this message]
2012-08-07 17:56 ` David Rothenberger
2012-08-08 13:14 ` Warren Young
2012-08-07 7:00 ` Achim Gratz
2012-08-07 7:38 ` Warren Young
2012-08-07 5:07 ` Christopher Faylor
[not found] ` <CABVhxxJ_nsTF3o85nWJsRdMOq38LYr2R9b9H8ATHfNCCqnmbqw@mail.gmail.com>
2012-08-07 14:05 ` Michael Gundlach
2012-06-14 19:48 Rolf Campbell
2012-06-14 19:55 ` Christopher Faylor
2012-06-14 20:09 ` Rolf Campbell
2012-06-14 22:00 ` Garrison, Jim (ETW)
2012-06-14 22:02 ` Garrison, Jim (ETW)
2012-06-15 10:38 ` Warren Young
2012-06-15 13:24 ` Rolf Campbell
2012-06-15 13:43 ` Rolf Campbell
2012-06-19 9:32 ` Adam Dinwoodie
2012-06-19 19:24 ` Rolf Campbell
2012-06-19 21:19 ` Achim Gratz
2012-06-20 0:22 ` Warren Young
2012-06-20 5:25 ` Achim Gratz
2012-06-26 16:46 ` Achim Gratz
2012-06-26 17:25 ` David Rothenberger
2012-06-26 18:07 ` Achim Gratz
2012-06-27 9:11 ` Adam Dinwoodie
2012-06-27 14:07 ` Achim Gratz
2012-06-27 18:18 ` David Rothenberger
2012-06-27 18:41 ` Achim Gratz
2012-06-28 11:49 ` Achim Gratz
2012-06-28 16:31 ` David Rothenberger
2012-06-28 19:04 ` Achim Gratz
2012-06-28 19:27 ` David Rothenberger
2012-06-28 20:40 ` Achim Gratz
2012-07-11 6:34 ` Achim Gratz
2012-07-11 7:07 ` marco atzeri
2012-07-11 7:48 ` Achim Gratz
2012-07-11 17:19 ` marco atzeri
2012-06-28 17:37 ` Rolf Campbell
2012-06-28 19:11 ` Achim Gratz
2012-06-28 20:03 ` Warren Young
2012-06-28 20:35 ` Achim Gratz
2012-06-28 21:17 ` Warren Young
2012-06-28 20:37 ` David Rothenberger
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=CABVhxxKA9oDn8KEwgVjpxL2Qke+TzpjteoJRFuiXHk13URV64A@mail.gmail.com \
--to=adblockforchrome@gmail.com \
--cc=cygwin@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).