Then what about a more complicated scenario like
below:
(1) I have made a few changes in my local workspace
and committed all these changes into the repository.
(2) I have not done any work for a few days. However
during these few days, someone commits whole bunch of
changes into the repository.
Now I want to make a tag based on the revisions of all
the files in my local workspace. Is this possible? Or
is it possible to figure the revision number of the
root directory corresponding to my local workspace?
--- Gavin Lambert <gavinl@compacsort.com> wrote:
> Quoth Kevin Hung <mailto:cykhung@yahoo.com>:
> > But then what if I have a lot of directories and
> > files? I know that I can "copy" recursively from
> the
> > top-level directory and do the copy based on the
> > version number of the top-level directory. But how
> do
> > I know the relationship between the version number
> of
> > the top-level directory and the version number of
> any
> > particular file?
>
> Do the copy based on the highest-numbered revision
> that you want to copy
> (which will be the file's revision, not the
> top-level folder's
> revision).
>
> So if you've done a commit and the files involved in
> the commit got
> listed as revision 67, then copy from the root dir
> with -r67. It
> doesn't matter what revision the top-level dir says
> -- that's the latest
> revision that the folder itself got changed, which
> usually won't
> correspond with the changes you just made. And the
> next commit that
> anyone makes, no matter where in the repository they
> make it, will be
> assigned the next revision number (68), which means
> that you'll exclude
> it from your copy.
>
>
__________________________________
Start your day with Yahoo! - Make it your home page!
http://www.yahoo.com/r/hs
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 14 07:08:38 2005