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

Re: The "follow copy history" initiative

From: Ben Reser <ben_at_reser.org>
Date: 2004-04-02 10:05:05 CEST

On Fri, Apr 02, 2004 at 07:37:18AM +0200, C.A.T.Magic wrote:
> C. Michael Pilato wrote:
> >Greg Hudson <ghudson@MIT.EDU> writes:
> >>I'm not saying it's never useful to know what copies of a node were made
> >>in the past or the future. But the purpose of this function is to aid
> >>commands like "svn cat -r N filename", and that should not traverse
> >>copies going forward.
> >
> >FWIW, I agree with you.
>
> it's probably VERY useful -
> ( copied from thread "Dropping Subversion" )
>
> cvs status -v foo
> ===================================================================
> File: foo Status: Up-to-date
>
> Working revision: 1.4
> Repository revision: 1.4 /CVS/Project/foo,v
> Sticky Tag: (none)
> Sticky Date: (none)
> Sticky Options: (none)
>
> Existing Tags:
> foo-V01-00 (revision: 1.1)
> foo-V02-00 (revision: 1.2)
> foo-V03-01 (revision: 1.3)
> foo-V04-03 (revision: 1.4)
>
> this would require an svn command for something like
> 'list all node-copies of this file|dir that currently exist in -rHEAD
> below /tags or /branches'

This is an entirely different issue. Has nothing to do with what
they're talking about in this thread. Please don't mix and match
threads.

-- 
Ben Reser <ben@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 2 10:05:37 2004

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.