> > So i guess there is a flaw in the api of svn itself.. you should just be
> > able to set the status to what you want..
> > or a command: revert to local working copy...
> I do not agree this is a flaw and I'd guess you have zero chance of
> ever getting an API like that from the Subversion developers.
> Statuses are generally calculated on the fly. For example, there is
> no stored state that a file is modified. This is something it
> determines by checking the file when you ask for the status.
> Scheduled add, delete and replace are stored in the working copy and
> Subversion gives you an API -- revert, to undo that.
So you are saying, that deleting a changed file and then undo that because
it was an accident
that the state of svn will be completely wrong and that it will always be
impossible to revert that
to the right state? (outgoing change)
thats really not a solution.. how can we work around that?
If it is true that the state is just by checking the file. how come that it
has a delete state?
Where is that being kept? how can i get rid of that?
Because if we do that then it will be automatically fine if i read you email
because the status is calculated.. (which is perfect then)
Received on 2008-05-08 15:39:15 CEST