Re: prop ops on schedule-delete

"Ed Price" <ed.price@gmail.com> writes:
> So you think they should be inconsistent but in the opposite way they
> are inconsistent now. Interesting :) Actually, I can see where you're
> coming from, I think... There is no value is changing the properties
> of a to-be-deleted file (AFAICS) but there *is* value in querying
> properties it had prior to deletion.

Exactly.

> Hmm. I think you've changed my mind. I would now propose:
>
> * propget and proplist should Just Work on schedule-delete
>
> * propset and propedit should return a warning that the file is
> scheduled for deletion.

What about --force to override? (Assuming you meant "error" where you
wrote "warning" above -- warnings are not fatal and therefore are
usually not "returned" from operations, they are merely printed.)

> Should I file this as an issue?

+1 to that.

> I think you misread the output. There was no error message for any of
> the ops on schedule-delete file. But one of the ops silently returned
> the wrong answer.

Yup, sorry about that (I was in the middle of something else and just
checking mail while some data copied, my bad...)

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 13 00:29:31 2006