Re: after commit folder is considered out of date but why not other files?

On Feb 3, 2008, at 07:06, Kent Tong wrote:

> Suppose a project contains two files: F1 and F2. After modifying F1
> and
> committing the project,
> I understand that both the project folder and F2 are also brought
> to a new
> revision. My question
> is, why is the folder considered outdated but F2 is not? For
> example, I can
> set a property on
> both and if I try to commit, it works fine on F2 and will fail on the
> folder. After all there has no
> changes to the folder. Why is it considered out of date?

I believe this is a bug:

http://subversion.tigris.org/issues/show_bug.cgi?id=1539

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-03 17:52:49 CET