From owner-svn-src-all@FreeBSD.ORG Fri Jan 2 06:45:11 2009 Return-Path: Delivered-To: svn-src-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB3B8106564A; Fri, 2 Jan 2009 06:45:11 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk1.360sip.com [72.236.70.240]) by mx1.freebsd.org (Postfix) with ESMTP id B0BB88FC0C; Fri, 2 Jan 2009 06:45:06 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from [192.168.28.129] (d75-157-251-204.bchsia.telus.net [75.157.251.204]) (authenticated bits=0) by sippysoft.com (8.13.8/8.13.8) with ESMTP id n026j49s090351 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Jan 2009 22:45:05 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Message-ID: <495DB7DF.5020603@FreeBSD.org> Date: Thu, 01 Jan 2009 22:44:47 -0800 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Doug Barton References: <200901011055.n01AtQaN052763@svn.freebsd.org> In-Reply-To: <200901011055.n01AtQaN052763@svn.freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: svn: head/usr.sbin/mergemaster X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jan 2009 06:45:12 -0000 Doug Barton wrote: > Given that this is a situation that comes up very infrequently (usually > only for a major version upgrade) and can usually be handled simply > enough on a one-off basis, I will once again point out that I think > this is a Bad Idea. I would be willing to consider a better implementation > as an option that is off by default. You are very wrong on this. This situation happens very *frequently* even for updates between minor releases (such as 6.3 to 6.4 and so on). As somebody doing lot of source upgrades frequently I can tell you this for sure. -Maxim