[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Copy/move-handling on update in 1.5

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2007-11-15 15:28:44 CET

On Nov 15, 2007 8:18 AM, Erik Huelsmann <ehuels@gmail.com> wrote:
> On 11/15/07, Mark Phippard <markphip@gmail.com> wrote:
> > On Nov 15, 2007 8:58 AM, Erik Huelsmann <ehuels@gmail.com> wrote:
> > > On 11/15/07, Freddie Albertsman <c03fan@cs.umu.se> wrote:
> > > > Hi Tor!
> > > >
> > > > I'm working on the copy-on-update problem; it works actually when the delete
> > > > happens after the add. I'm working on a solution that would always make the
> > > > delete happens at the very end.
> > > >
> > > > I haven't come across any example either that makes the scenario you
> > > > presented (copy on update) behave normally.
> > >
> > > If I'm correct, deletes are inherently sent before adds because we had
> > > problems with case-sensitivity before: if a file is renamed from
> > > THIS-FILE to this-file and the Add is sent before the delete, Windows
> > > gets confused (heavily). To resolve this problem, Adds are sent before
> > > Deletes, afaik.
> >
> > That is also what I thought ... except I think you meant to say
> > Deletes are sent before Adds.
>
> Heh. ofcourse I meant to say that.

I think that what you mean to say is that *within a single directory*,
deletes are always sent before adds.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 15 15:29:12 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.