On Sat, 2005-01-29 at 21:23, Gil Megidish wrote:
> Hey.
>
> First of all, kudos for this GREAT book. I have been working with cvs
> and subversion and I thought I should give it a try and read the
> entire book, learn new things. Book is written beautifully, and
> smoothly. Thanks for everyrthing. During my reading, I found this: I
> think Makefile and integer.c should have revision 5. No?
>
> -- gil
>
>
> =======================================================================
>
> 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
>
"svn commit button.c" creates revision 5 in the repository and button.c
in the working copy is also now at revision 5. But the other files
continue be at the previous revision. A typical svn working copy
is made up of files at various revisions. 'svnversion path' is
useful for checking mixed revisions.
> Suppose that, at this point, Sally commits a change to integer.c,
> creating revision 6. If you use svn update to bring your working copy
> up to date, then it will look like this:
>
> calc/Makefile:6
> integer.c:6
> button.c:6
svn up, unless you specify a target updates recursively, by default to
the HEAD revision.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 31 06:45:42 2005