On Mon 2003-03-17 at 20:43:46 -0600, Karl Fogel wrote:
> Benjamin Pflugmann <benjamin-svn-dev@pflugmann.de> writes:
> > I am not sure if I am missing something, but if I get to see the base
> > version, I would expect to see the base propr, too. I always
> > understood that -r BASE theoretically gives me the same I would get if
> > I stated the reversion explicitly and queried the repository (by using
> > an URL). Isn't that the case for all commands?
>
> Yes, that's right.
>
> Most commands default to the working file, and then you can use -rBASE
> or -rHEAD or whatever to specify otherwise.
>
> The only reason to make 'svn cat' different from this is that catting
> the working file is fairly useless. You could just do plain 'cat' for
> that.
I understood that. I have no strong opinion about the default (except
that it should be one of -rBASE or WC file). My comment was about the
props: If -rBASE is chosen as default, props should taken from BASE,
too, i.e. it should behave as if I would specify BASE explicitly and
just documented as meaning that.
> I dunno.
For the "text" case, I do neither.
> Maybe consistency is more important?
Consistency is always nice, if it comes with low cost. I presume that
if I want the base revision, I would add -rBASE without thinking about
it, because that is usually needed anyhow (for any of the other
commands).
> I wish I had a stronger opinion, one way or the other :-).
:-)
If would suggest that if there is the possibility that "svn cat" does
more than dump printing, it should default to the WC. Else, I don't
care.
As an (maybe stupid) example: If I could use a switch to svn cat to
change keyword expansion (including reversing it), that would be
potentially useful to apply to the WC. If -rBASE is default, is there
an easy way to specify that I want the WC instead (sorry for being
ignorant here)?
Benjamin.
- application/pgp-signature attachment: stored
Received on Tue Mar 18 06:20:22 2003