Hi, I use PuTTY all the time, including yesterday and today, without problems. I did update to the latest PuTTY client (v0.58 IIRC) a couple of weeks ago for an unrelated reason. I did not have to change any settings in my PUTTY clients to get it to use ssh v2, or anything like that.
Yoav Shapira System Design and Management Fellow MIT Sloan School of Management Cambridge, MA [EMAIL PROTECTED] / [EMAIL PROTECTED] > -----Original Message----- > From: Mark Womack [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 27, 2005 9:52 AM > To: Log4J Developers List > Subject: Re: log4j 1.2.12 status > > So, I had some complications connecting to cvs yesterday. cvs.apache.org > has been updated to a new version of FreeBSD, and a new ssh protocol > (version 2) is used. My PuTTY client would not connect properly. This > morning I tried changing my PuTTY settings to use ssh v2, but now it > crashes. > > How are others connecting to cvs? Anyone else use PuTTY? > > I'll be trying again tonight. > > -Mark > > ----- Original Message ----- > From: "Mark Womack" <[EMAIL PROTECTED]> > To: "'Log4J Developers List'" <[email protected]> > Sent: Tuesday, July 26, 2005 9:31 AM > Subject: RE: log4j 1.2.12 status > > > > I'm going to generate a build for 1.2.12 this evening. Everyone that > has > > fixed a bug since 1.2.11 should make sure the docs/HISTORY.txt is up to > > date > > with the bug fix info. > > > > -Mark > > > >> -----Original Message----- > >> From: Curt Arnold [mailto:[EMAIL PROTECTED] > >> Sent: Friday, July 22, 2005 4:07 PM > >> To: Log4J Developers List > >> Subject: log4j 1.2.12 status > >> > >> I've taken a pass through the 1.2.12 bug list (searching for log4j > >> bugs with the word "candidate" in a comment) and killed off the ones > >> that I wanted to and left the icky ones for everybody else. I'm > >> going to have to work on something else for a while. > >> > >> The following bugs still seem to be pending for a 1.2.12 release: > >> > >> Javadoc related (14551, 17227, 18122, 30804, 30819) > >> > >> Bug 26345 involves a class loader issue which I'm always hesitant to > >> touch. Unless someone feels real confident that the change is > >> innocuous, I wouldn't feel bad letting it slip to 1.3 or a later 1.2.x. > >> > >> Bug 33624, a SocketHubAppender issue, is assigned to Mark. It > >> doesn't look like we have a handle on it, and it might be one to do > >> in the CVS HEAD and backport to a later log4j 1.2.x if there is such > >> a thing. > >> > >> Bug 34026 involves the interpretation of ignoresThrowable on the > >> SyslogAppender. > >> > >> Bug 31727: Appears to be Chainsaw related. > >> > >> > >> The following I don't believe should be attempted in log4j 1.2.12: > >> > >> Bug 22894 involves the undesirable interpretation of Java-like escape > >> sequences in XML configuration files which causes Windows filepaths > >> to be misinterpreted. I did a fix in log4j 1.3, but I'm not happy > >> with it and don't see a clean enough way to fix it in log4j 1.2 since > >> existing configuration files may expect the behavior. > >> > >> Bug 24519 would likely require seriously reworking the > >> synchronization in log4j and is likely a 2.0 issue. > >> > >> I think the current branch is close enough to start thinking about > >> working up a release candidate. > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
BEGIN:VCARD VERSION:2.1 N:Shapira;Yoav FN:[EMAIL PROTECTED] ORG:MIT Sloan School of Management TITLE:System Design and Management Fellow URL;WORK:http://www.yoavshapira.com EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20050611T145830Z END:VCARD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
