Thanks for the clarification Ryan. I had noticed that it is not recent
unless you update to current or checkout the latest. I'm actually using
in the context of a full loadbuild which always checks out the latest
version before doing a build, so i should be okay.
Yong.
On Wed, 2006-01-25 at 18:19 +0100, Ryan Schmidt wrote:
> On Jan 25, 2006, at 17:21, Yong Lee wrote:
>
> > On Wed, 2006-01-25 at 17:57 +1100, Lakshman Srilakshmanan wrote:
> >
> >> The "Last Changed Rev: 5357" indicates the last revision number
> >> when a
> >> change affected this directory or beneath it.
> >>
> >> The "Revision: 5403" is the last revision number used to change a
> >> project.
> >
> > I am using this against the top level project dir to determine the
> > last
> > update to have affected a project and I just wanted to be sure that
> > this
> > was a valid method. My initial tests were showing this behaviour
> > but I
> > wanted to be sure i was seeing what I thought i was seeing :)
>
> It is valid, so long as the root directory is up-to-date. But if you
> haven't run "svn up" lately, then it'll only show you the last
> changed revision as of the last time you ran "svn up". This is one of
> the side-effects of allowing mixed-revision working copies.
>
> You may want to use the "svnversion" command instead, which takes
> longer to execute but gives you an accurate answer every time.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 25 19:13:32 2006