From owner-svn-src-user@FreeBSD.ORG Thu Oct 24 09:03:51 2013 Return-Path: Delivered-To: svn-src-user@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D6ECE52B; Thu, 24 Oct 2013 09:03:51 +0000 (UTC) (envelope-from ray@freebsd.org) Received: from smtp.dlink.ua (smtp.dlink.ua [193.138.187.146]) by mx1.freebsd.org (Postfix) with ESMTP id 93B722808; Thu, 24 Oct 2013 09:03:51 +0000 (UTC) Received: from terran (unknown [192.168.99.1]) (Authenticated sender: ray) by smtp.dlink.ua (Postfix) with ESMTPA id E7D60C493D; Thu, 24 Oct 2013 12:03:43 +0300 (EEST) Date: Thu, 24 Oct 2013 12:05:15 +0300 From: Aleksandr Rybalko To: Benjamin Kaduk Subject: Re: svn commit: r256970 - user/ed/newcons/sys/dev/vt Message-Id: <20131024120515.da8ad392b7b3849b752ae1f2@freebsd.org> In-Reply-To: References: <201310231415.r9NEFkXT003267@svn.freebsd.org> X-Mailer: Sylpheed 3.2.0 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "src-committers@freebsd.org" , svn-src-user@freebsd.org X-BeenThere: svn-src-user@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the experimental " user" src tree" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Oct 2013 09:03:51 -0000 On Wed, 23 Oct 2013 11:06:49 -0400 Benjamin Kaduk wrote: > On Wed, Oct 23, 2013 at 10:15 AM, Aleksandr Rybalko wrote: > > > Author: ray > > Date: Wed Oct 23 14:15:46 2013 > > New Revision: 256970 > > URL: http://svnweb.freebsd.org/changeset/base/256970 > > > > Log: > > Turn off confusing rotation of scroll history. > > > > Thanks! I saw that in the quarterly status report and was thinking to > myself, "gosh, a fully cyclic history buffer might get confusing", so it's > good to hear that it's fixed. > > -Ben np Ben! It was mostly not about how it work, but how it is implemented. So code should not care where is end of buffer, but just always write into it. WBW -- Aleksandr Rybalko