From owner-freebsd-questions@FreeBSD.ORG Wed Jan 23 02:19:39 2013 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 23B74FF1; Wed, 23 Jan 2013 02:19:39 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:6:4]) by mx1.freebsd.org (Postfix) with ESMTP id 48DF720E; Wed, 23 Jan 2013 02:19:37 +0000 (UTC) Received: from ppp247-71.static.internode.on.net (HELO leader.local) ([203.122.247.71]) by ipmail04.adl6.internode.on.net with ESMTP; 23 Jan 2013 12:49:31 +1030 Message-ID: <50FF4863.9060800@ShaneWare.Biz> Date: Wed, 23 Jan 2013 12:48:11 +1030 From: Shane Ambler User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Peter Vereshagin Subject: Re: 'svn-export' incrementing? References: <20130123012915.GA16404@external.screwed.box> In-Reply-To: <20130123012915.GA16404@external.screwed.box> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: glarkin@freebsd.org, xyne@archlinux.ca, questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2013 02:19:39 -0000 On 23/01/2013 11:59, Peter Vereshagin wrote: > I believe there is something wrong in the way I use the 'svn-export'. > Otherwise it's a no problem for me to patch for '--force'. > > How can I update the already created 'work tree' with 'svn update'? > I think the correct answer is a good idea for 'Synopsis' docs > section. The command "svn export" exports a clean source tree - without revision control information. Basically a clean snapshot of the revision you export, intended as a sourcecode release version snapshot. It expects to be exporting to a clean directory which is why you need to force it to overwrite existing files. To "update" a source tree you need the revision information for svn to test what has changed, which you get with svn checkout and svn update