X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 30 May 2012 20:45:45 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Mintty Log Off problem (now 1.7.16s)
Message-ID: <20120530184545.GE26411@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4FC65ACB DOT 1070109 AT w5pny DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <4FC65ACB.1070109@w5pny.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On May 30 11:37, Harry G McGavran Jr wrote:
> Corinna wrote:
> 
> 
> >If the code in question has changed a lot, it's only marginally helpful
> >to refer to a change in older code.  OTOH, knowing both, which snapshot
> >"fixed" it and which snapshot broke it again could be valuable.
> >
> >
> >Corinna
> 
> This problem first appeared in 1.7.10.  The snapshot I downloaded
> that fixed it was "cygwin-inst-20120415.tar.bz2" that I downloaded
> on April 17, 2012.  The first go around of posts on this went
> without replies for quite some time after 1.7.10 came out.
> After one of my posts that questioned whether there were
> very many seeing this problem, someone posted that I should
> try the latest snapshot, so there is a chance the problem
> was fixed in a snapshot previously to the one I downloaded.
> The one I downloaded was current as of the day the post appeared
> suggesting a snapshot, so it could have been where the fix was.
> Nonetheless I responded to that post with a post saying that
> that snapshot fixed the problem.  There were no further
> posts on the subject until now.

That's why I'm asking.  If you could try to find out which snapshot
fixed it and which snapshot broke it again, it would help to find the
cause.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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