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

Re: Question: Rev 914

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-01-17 03:40:18 CET

David Summers <david@summersoft.fay.ar.us> writes:

> Ah yes, grasshopper. Dig deeper! :-)
>
> So how can I "ask the file system"? Is that the svnadmin command? If so,
> can that be done remotely through the network using svn client?
>
> Nit: The actual tag occurred as rev 914. Was that a copy of 909 or is the
> actual copy = rev 914 (files as of 913)?
>
> Inquring Minds want to know!

When the repository was at revision 913, Mike Pilato and I sat at his
desk and issued this command (not in a working copy, either!):

  svn cp -r 909 http://svn.collab.net/repos/svn/trunk \
                http://svn.collab.net/repos/svn/tags/0.8.0

Therefore, I'm certain that the 0.8.0 directory is a copy of /trunk in
r909.

But, now, grasshopper, I throw a question back at you: why do you
care to know what /tags/0.8.0 is a copy of? Is it not enough that it
merely exists?

I mean, when you tag 300 RCS files with CVS, do you care to examine
the exact list of per-file revisions that the tag represents?
Similarly, do you care to see the exact list of node-ids that live
beneath /tags/0.8.0?

[ One way of exploring: run 'svnadmin shell repo'. You can
  interactively explore the node-ids that way. Or if you want to know
  how /trunk differs from /tags/0.8.0, the 'svn diff' command should
  someday be able to do this. Finally, the 'svnlook' binary will
  someday describe copies as they occur, rather than mailing us 8 meg
  commit mails. ]

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:56 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.