Re: GSoC Progress report

2010-07-29 Thread Stefan Sperling
On Wed, Jul 28, 2010 at 10:55:39PM +0300, Daniel Shahaf wrote: > Stefan Sperling wrote on Wed, Jul 28, 2010 at 16:05:49 +0200: > > But there's no harm in making svn patch interpret existing move information > > in git diffs. We can carry out a corresponding copy + delete. > > We won't be generating

Re: GSoC Progress report

2010-07-29 Thread Branko Čibej
On 28.07.2010 12:06, Daniel Näslund wrote: > * base85 encode binary content > Does git do that? Hmmm ... I'd have used base64 myself, not quite as compact but a lot more existing tools and libraries understand it. -- Brane

Re: GSoC Progress report

2010-07-29 Thread Branko Čibej
On 28.07.2010 21:55, Daniel Shahaf wrote: > Stefan Sperling wrote on Wed, Jul 28, 2010 at 16:05:49 +0200: > >> But there's no harm in making svn patch interpret existing move information >> in git diffs. We can carry out a corresponding copy + delete. >> We won't be generating move git diff head

Re: GSoC Progress report

2010-07-28 Thread Daniel Shahaf
Stefan Sperling wrote on Wed, Jul 28, 2010 at 16:05:49 +0200: > But there's no harm in making svn patch interpret existing move information > in git diffs. We can carry out a corresponding copy + delete. > We won't be generating move git diff headers ourselves, but we should > be interoperable with

Re: GSoC Progress report

2010-07-28 Thread Stefan Sperling
On Wed, Jul 28, 2010 at 12:06:11PM +0200, Daniel Näslund wrote: > Hi! > > Property diffs > === > * We can create parseable prop patches > * We can parse property patches > * We can match property patches > * We can write patched properties to tmp files > * We can install those prop cha

GSoC Progress report

2010-07-28 Thread Daniel Näslund
Hi! Property diffs === * We can create parseable prop patches * We can parse property patches * We can match property patches * We can write patched properties to tmp files * We can install those prop changes to files and dirs (not the wc-root dir yet) Todo -- * Decide on how we w