On Tue, Dec 08, 2009 at 07:20:19PM +0100, d.sastre.med...@gmail.com wrote:
> On Tue, Dec 08, 2009 at 07:46:27AM -0700, Warren Young wrote:
> > Personally, I'd just back that directory *and* all the Cygwin
> > registry sub-trees up and go ahead with the upgrade-in-place.
> > Parallel Cygwin installs
On Tue, Dec 08, 2009 at 07:46:27AM -0700, Warren Young wrote:
> Personally, I'd just back that directory *and* all the Cygwin
> registry sub-trees up and go ahead with the upgrade-in-place.
> Parallel Cygwin installs work, but there are annoyances.
I think I'll go this way.
> Given your evident c
Corinna Vinschen wrote:
On Dec 8 13:45, d.sastre.med...@gmail.com wrote:
I'm plannig to migrate my production env (i.e. my XPSP3 box at work
8-D), from 1.5.25 to 1.7 as soon as there is an official release,
There's no reason not to use the current beta.
True. Many of us have been using it
On Dec 8 13:45, d.sastre.med...@gmail.com wrote:
> I'm plannig to migrate my production env (i.e. my XPSP3 box at work
> 8-D), from 1.5.25 to 1.7 as soon as there is an official release,
There's no reason not to use the current beta. The current 1.7.0-68
is probably equivalent to the official 1.
Hello,
I'm not a contributor to this list (yet), but a fan reader, and
I wanted to show my appreciation and gratitude for bringing
CYGWIN. To me, WIUWI.
I have been reading (not thoroughly enough yet)
FAQ/features/changes/user guide for the next 1.7 release, and I have
some questions:
I'm plann
5 matches
Mail list logo