kmradke_at_rockwellcollins.com wrote on 02/21/2008 03:30:58 PM:
> dglasser_at_gmail.com wrote on 02/21/2008 03:18:09 PM:
> > On Thu, Feb 21, 2008 at 4:06 PM, <kmradke_at_rockwellcollins.com> wrote:
> > > I guess I'm most interested in the user interface, not the low
level
> > > interface. I've always assumed you couldn't 'svn propset' on
> > > an existing property, you had to 'svn propedit'. Therefore the
> > > property interface should be no different than the file contents
> > > interface (to the end user).
> > >
> > > I've found it quite annoying that you need the file contents
> > > in a working copy just to modify file properties. We have some
> > > 2G+ files and it is really annoying to have to check them out
> > > just to add svn:needs-lock...
> >
> > Yes, and you can now use propedit to add svn:needs-lock on an URL.
> > (Just not to delete it, I guess.)
>
> Hmmm.... Didn't know propedit would allow you to add a non-existing
> property. Bad assumption on my part. It gets a little ugly if
> you want to script something with propedit since it wants to open
> an editor for the values.
On a positive note, I was able to hack the trunk version of
'svn propdel' to take a base revision parameter to allow me to
delete the incorrect 'svn:special' properties on the files
that were causing the checkout problems.
I used the -r parameter instead of creating a new --base-rev
option. Is a new option warranted? Is there precedence for --base-rev?
I'm willing to create a patch, but need some direction on
how this should really work.
Kevin R.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-02-21 23:04:14 CET