Re: commit of out-of-date WC with mod'd dir props fails - why?

From: Alexis Huxley <ahuxley_at_gmx.net>
Date: 2002-07-15 22:35:17 CEST

> > I guess there is some logic to this, but I cannot see it. Could
> > someone explain please? Thanks.
>
> Propchanges on directories can only be committed if the directory is
> at HEAD. This is currently our "one inflexibility" in the way we
> allow mixed-revision working copies.
>
> For an explanation, read /doc/user/manual/dirversioning.texi. In
> particular, read the "overeager directory" problem.

Ah ... Damn ... I should start searching closer to home, thanks
Ben.

Out of curiousity, is this likely to be the way it stays, or
is a solution - even if a very long way off - likely to be implemented?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 15 22:36:02 2002

This message: [ Message body ]
Next message: Ben Collins-Sussman: "Re: commit of out-of-date WC with mod'd dir props fails - why?"
Previous message: Karl Fogel: "Re: [PATCH] Issue #763"
In reply to: Ben Collins-Sussman: "Re: commit of out-of-date WC with mod'd dir props fails - why?"
Next in thread: Ben Collins-Sussman: "Re: commit of out-of-date WC with mod'd dir props fails - why?"
Reply: Ben Collins-Sussman: "Re: commit of out-of-date WC with mod'd dir props fails - why?"

Contemporary messages sorted: [ By Date ] [ By Thread ] [ By Subject ] [ By Author ] [ By messages with attachments ]