Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (herse.apache.org: domain of peter.j.donald@gmail.com
 designates 64.233.184.235 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=m6j/rhEkQTsb5A4wV6MWQvQkUbUnPhYk58XKwqa46xCt3/QdsKT6g7hhnyz8ZDCcjYa7xvkbdSc6cIfbO8Ij3331c048GbROMOsFprmrt0N6oMViRPWfEb31gf8KYlUywMXUQjCj+xbIkapiMAlmvy+lo5TYwGxolZvmTngCGTk=
Message-ID: <125c0c0d0701081356v5d9719f6l8dfadf64dae9961@mail.gmail.com>
Date: Tue, 9 Jan 2007 08:56:26 +1100
From: "Peter Donald" <peter@realityforge.org>
Sender: peter.j.donald@gmail.com
To: dev@harmony.apache.org
Subject: Re: [classlib][pack200] new module (was: [classlib][pack200]
 Development has stalled :-( )
In-Reply-To: <200701082318.01315.gshimansky@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <2c9597b90701061246j749bd7ccydc48ae15415d674d@mail.gmail.com>
	 <58B90A37-56BE-442D-B9B1-E52EAB89516C@pobox.com>
	 <125c0c0d0701071925m2fe3e327o8d3495118eae63df@mail.gmail.com>
	 <200701082318.01315.gshimansky@gmail.com>

On 1/9/07, Gregory Shimansky <gshimansky@gmail.com> wrote:
> This pretty much reminds me of what GIT is capable of doing and how it was
> used internally in Intel. You are building a chain of commits into a local
> repository, then create a patch which includes all changes in this chain. I
> am very curious about one aspect of this practice. If in the main repository
> in SVN some files affected by your chain of commits are changed, how hard it
> is to merge changes from the main latest revision of SVN repository with the
> chain that you've built locally, based on some earlier previous SVN revision?

It is trivial to do this under svk. I actually do the synchronization
with remote repo, merging into local branches and updating working
copys in separate steps but I believe you can do it in one step via
either "svk up -sm" or "svk pull" in a working copy.

-- 
Cheers,

Peter Donald