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

Re: Hello

From: Duncan Murdoch <murdoch_at_stats.uwo.ca>
Date: 2006-03-09 16:03:46 CET

On 3/8/2006 9:00 AM, Rahul_Sinha@external.mckinsey.com wrote:
> Hi,
>
> I was going thru the Subversion book 1.2
>
> Under chapter two :
> ------------------------------------------------
> At the moment, this working directory corresponds exactly to revision 4 in
> the repository. However, suppose you make a change to button.c, and commit
> that change. Assuming no other commits have taken place, your commit will
> create revision 5 of the repository, and your working copy will now look
> like this:
> calc/Makefile:4
> integer.c:4
> button.c:5
> ----------------------------------------------------------------------
> I believe its should be "5" for Makefile: & integer.c: also.
> Plz comment.

The book is right. svn won't update those other files unless you ask it
to do so.

In this particular example it's not all that important, since rev 4 and
5 of those files are identical, but if you use svnversion to find out
the current version of your working copy, you'll see that you have a
mixed revision.

Where it becomes important is if someone else modifies and commits (e.g.
committing changes to Makefile) creating rev 6, then you modify and
commit button.c again. You'll now have rev 7 of button.c and still have
rev 4 of the rest, which may no longer be identical to the HEAD revision.

This is why it's a good practice to update frequently. Then all your
files are in a consistent state.

Duncan Murdoch

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 9 16:28:29 2006

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