Ed Price writes:
> > > Should I file this as an issue?
> > +1 to that.
> Given the discussion I'm glad to see has now occurred, I'm not
> sure how to file this.
> Once Julian disagreed that prop ops should work on schedule-delete
> I looked into other operations on schedule-delete; the following
> commands appear to work (ie don't print an error or warning):
> svn blame
Should work, will blame the BASE revision of the file.
> svn cat
Dito. (If there's a bug that cat'ing the WORKING file works, then
that's a bug that doesn't affect the cmdline client currently.)
> svn delete
Could warn, current behaviour confusing IMO.
> svn export
Seems like a bug when no revision specified.
> svn list
Should work IMO, since it lists repository items. It could be said to
work on BASE as well.
> svn lock
Seems reasonable that this works. You could prevent others from
working on a file you deleted.
> svn log
Why shouldn't this work?
> svn merge
I don't see a reason this should work.
> svn propdel, propedit, propget, proplist, propset
I agree with those who think this should *not* work. Well, I think
proplist should work when a revision is specified.
> svn resolved
Hmmm... Shouldn't deleting a file automatically resolve it?
> svn status
Should work and say "D path".
> svn unlock
> svn update (expected?)
> What about update? (Current behavior appears to
> be that if the file has no updates, it stays deleted,
> but if it has updates, it gets "undeleted". If one modifies
I'd say this should be a tree conflict.
> the file in the WC, then svn deletes it, then updates it,
> it does *not* cause a conflict, it's the same as if it had
> not been modified prior to deletion... Which doens't
> seem so wrong. AFAIK there's no way to undelete
> a file and yet retain its pre-delete modifications --
> revert will revert both the delete and the changes...
> OTOH maybe that's not a good thing. Maybe there
> should be a way to just "undelete" a file without
> reverting any pre-delete local changes?)
I don't think so, but that's unrelated.
I'm probably missing some points in my walk-through above which others
will point out:-) I think it would be appropriate to file an issue
about certain commands having bad/confusing interaction with schedule
delete files linking to this thread. Then we could add a "final" list
of things that should be fixed to that issue when the discussion is
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Mar 13 16:07:04 2006