X-Spam-Check-By: sourceware.org Message-ID: <001201c6945d$59ca3010$0a3b6080@joehome> From: "Science Guy" To: Subject: snapshots: first resort, or last resort? Date: Tue, 20 Jun 2006 07:33:22 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook Express 6.00.2800.1807 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com In http://cygwin.com/ml/cygwin/2006-06/msg00434.html, Brian said "using the latest snapshot should always be the first thing you try when encountering a problem before reporting it to the list." However, the instructions for installing snapshots at http://cygwin.com/faq/faq-nochunks.html#faq.setup.snapshots say: "First, are you sure you want to do this? Snapshots are risky. They have not been tested. Use them ONLY if there is a feature or bugfix that you need to try, and you are willing to deal with any problems, or at the request of a Cygwin developer." For a non-expert, such as me, this dichotomy of views is perplexing. This is made all the more perplexing because there does not seem to be (I could not find) a user-readable list of bugs that each snapshot fixes vis-a-vis the latest release. So how would a user know whether the "risky" step of installing a snapshot will have any chance of fixing a particular bug? -- Joe -- 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/