public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Baurjan Ismagulov <ibr@ata.cs.hun.edu.tr>
To: cygwin@cygwin.com
Subject: Re: dll version collision
Date: Fri, 28 May 2004 20:46:00 -0000	[thread overview]
Message-ID: <20040528194634.GA1325@ata.cs.hun.edu.tr> (raw)
In-Reply-To: <20040528190550.GB5391@coe.bosbc.com>

Hello, Christopher!

On Fri, May 28, 2004 at 03:05:50PM -0400, Christopher Faylor wrote:
> You use the same technique as if you were testing another version of
> linux.  Or you'd backup your system prior to updating cygwin.  It is not
> likely that you could have two installations running on the same system
> with no bleed between them.

Well, with UML I have a reasonable environment to test most of things I
have to deal with. I would be happy to see the same for cygwin.


> Having two versions of cygwin working at the same time is not a goal
> for the cygwin project.

Does this mean that if someone comes with a clean patch doing that, it
would not be accepted? Once it were there, it wouldn't require
maintenance, any kind of user support can be explicitly disclaimed. What
kind of problems do you expect?


With kind regards,
Baurjan.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2004-05-28 19:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 22:22 Michael Hale
2004-05-27 23:09 ` Baurjan Ismagulov
2004-05-27 23:50   ` Igor Pechtchanski
2004-05-28 17:14     ` Michael Hale
2004-05-28 17:43       ` Christopher Faylor
2004-05-28 18:48         ` Michael Hale
2004-05-28 19:25           ` Reini Urban
2004-05-28 19:36             ` Michael Hale
2004-05-28 19:58           ` Christopher Faylor
2004-05-28 20:46             ` Baurjan Ismagulov [this message]
2004-05-28 21:04               ` Christopher Faylor
2004-05-28 21:43                 ` Baurjan Ismagulov
2004-05-28 22:51     ` Baurjan Ismagulov

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=20040528194634.GA1325@ata.cs.hun.edu.tr \
    --to=ibr@ata.cs.hun.edu.tr \
    --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).