Paul L Lussier <pll@lanminds.com> writes:
> In a message dated: 01 May 2003 22:46:48 CDT
> cmpilato@collab.net said:
>
> >Or, if the community thinks it useful, we could make 'svn propedit -R'
> >simply *not* populate the editor with anything, and instead skip
> >straight to storing your new property recursively. I'd wouldn't mind
> >that so much (as long as it was properly documented).
>
> Are you saying that 'svn propedit -R' would first pop up into an
> editor for the creation/modification of the prop, then recursively
> apply it? Or are you saying that you'd never get the editor at all,
> and the prop would have to be set by way of some other means,
> e.g. command line option or something?
The former. The addition of the -R would cause only two changes to
the way that propedit works today:
1) the editor would always be loaded with an empty file (instead of
any current property value(s), if such exist).
2) the new property value would be applied to the targets of the
recursion.
> I think the former would be useful, I think the latter would be
> confusing to too many. Unless 'svn propedit' is re-designed to take
> it's properties from STDIN, in which case, you can redirect a file con
> taining the properties to it. IOW:
[frightening ideas removed]
> Just some thoughts, do with them what you will :)
Good Lord, man, go back to bed and don't get up again until you stop
talking about redirected I/O! :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 2 15:39:12 2003