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

Re: peg revisions and cat.

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2005-06-20 05:38:28 CEST

Vivek <vivek@collab.net> writes:

> Cat takes peg revisions into consideration. Currently this is what
> happens:
> [vivek@vivek wc 14:55:13]$ svn cat add1@4
> Thu Jun 9 12:19:13 IST 2005
> Sat Jun 18 14:40:27 IST 2005
>
> [vivek@vivek wc 14:57:26]$ svn cat add2
> Thu Jun 9 12:19:15 IST 2005
>
> [vivek@vivek wc 14:57:45]$ svn cat add1 add1@1 add2
> Thu Jun 9 12:19:13 IST 2005
> Sat Jun 18 14:40:27 IST 2005
> subversion/libsvn_fs_fs/tree.c:313: (apr_err=160013)
> svn: File not found: revision 1, path '/add1'
>
> And :
> [vivek@vivek wc 14:58:39]$ svn cat add1 add1@5 add2
> Thu Jun 9 12:19:13 IST 2005
> Sat Jun 18 14:40:27 IST 2005
> subversion/libsvn_fs_fs/fs_fs.c:1142: (apr_err=160006)
> svn: No such revision 5
>
> Should these errors also be skipped?

I don't think so. The utility of skipping errors on unversioned
things is, I think, mostly so that folks can use globs in their
command-line input instead of picking each and every individual
versioned object from the set of all dirents. But it takes extra
effort to call 'svn cat' on a unversioned target *with a peg
revision*, so I'm less inclined to "let it slide" with a skipped
error.

I'm not thoroughly hung up on that opinion though, so put me at -0.5
for skipping those errors.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 20 05:41:03 2005

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