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

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

From: Kent Tong <kent_at_cpttm.org.mo>
Date: Sun, 3 Feb 2008 05:06:02 -0800 (PST)

Hi,

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?

-----

--
Kent Tong
Wicket tutorials freely available at http://www.agileskills2.org/EWDW
Axis2 tutorials freely available at http://www.agileskills2.org/DWSAA
-- 
View this message in context: http://www.nabble.com/after-commit-folder-is-considered-out-of-date-but-why-not-other-files--tp15253282p15253282.html
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
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 14:06:40 CET

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

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