Knowing when someone checks something out of the repository is not
the issue. This is because anyone with access can check things out. It
is knowing when things have been committed back into the repository that
there needs to be any concern, and Subversion provides ways to work with
that, primarily svn status and merge.
Yes this becomes a change in the way that your folks are working now;
think of it like copying sheet music at the library. You make a copy
from a book and take that home to play. Someone else does the same. It
is only if you need to update the original book to make a "permanent"
change that anyone needs to be concerned. (note I'm not advocating
"music theft" - too many friends who are musicians, including some of
the Subversion principles - just an example!!)
The key is running svn status and seeing what shape your working copy
(like the page of music you copied above) is in, and whether or not any
changes have been made that you may want to get. Bottom line is that
they won't have to walk down the hall to find out if someone has checked
something in. They can simultaneously make changes and the merge
process will show what changes, or conflicts, need to be resolved.
The book explains this fairly well, so perhaps a re-read of chapters
3 and 4 is in order.
It is possible to see all the log entries for a date range; this too
is documented on the svn log command.
Shawn Plummer wrote:
> I have a group of developers that are used to using CMS on VMS. I was
> introducing them to subversion today, which I am admittedly fairly new
> to myself, and they wanted to know about some functionality
> In CMS they are used to reserving a copy in the repository for editing,
> all this does is attach a tag to the file that such and such user has
> reserved the file, it prevents nothing from occurring to the file. They
> are a small group of developers and would like the ability to tell when
> someone has last checked out, or reserved, a file and not committed it
> yet so they could walk down the hall and talk to that person should
> they need to make changes to that file also.
> I feel this is a fairly awkward way to work, but they really like that
> ability. After reading over most of the manual, I cannot see a clear
> cut way to tell when a user last checked out something from the
> repository. Is this possible?
> Also is it possible to take a repository and see all changes made to it
> in the last year? this might be useful for managers to see and general
> Shawn Plummer
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Feb 25 17:19:45 2005