On Tue, Mar 4, 2008 at 11:58 AM, David Glasser <glasser_at_davidglasser.net> wrote:
>
> On Tue, Mar 4, 2008 at 8:54 AM, Mark Phippard <markphip_at_gmail.com> wrote:
> > On Tue, Mar 4, 2008 at 11:52 AM, David Glasser <glasser_at_davidglasser.net> wrote:
> > > On Tue, Mar 4, 2008 at 8:46 AM, Mark Phippard <markphip_at_gmail.com> wrote:
> >
> >
> > > > Paul touched on that. The issue is that merge is like an edit of the
> > > > working copy. On Windows and OSX, you cannot do a case only-rename of
> > > > a file. You can receive an update because it is altering the working
> > > > copy as it goes.
> > >
> > > Sorry, I don't follow. How does a merge not act like an update here?
> >
> > Merge can be reverted, so both copies of the file need to remain in
> > the WC text-base.
>
> Oh, right! The issue is the text-base! Sorry, I didn't completely follow.
>
> (wc 2.0 can solve this isssue by storing text-bases (and any other
> pieces of content worth tracking) in a content-hash-addressable
> store.)
I wasn't proposing anything so dramatic as solving *all*
case-insensitivity problems (query the issue tracker for "case" in the
summary field there are many), rather I was asking if it was worth
trying to mitigate the impact of this particular problem -- see
suggestions 1) and 2) at the start of this thread.
Paul
P.S. Added issue #3115 (hopefully Erik isn't about to point me to the
exact same issue already in there...)
> --dave
>
> --
> David Glasser | glasser@davidglasser.net | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-04 18:13:36 CET