Re: [Subclipse-dev] why is it that if i copy/paste over a file that it is then an outgoing deletion?

On Thu, May 8, 2008 at 9:39 AM, Johan Compagner <jcompagner_at_gmail.com> wrote:

> > > 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)

You delete the file it is gone. Subversion does not store it for you
anywhere. If you revert, Subversion can only put back the pristine
version.

> thats really not a solution.. how can we work around that?

Eclipse Local History?

> If it is true that the state is just by checking the file. how come that it
> has a delete state?

Because as I said, scheduled add, delete and replace are states that
are stored until you commit.

> Where is that being kept? how can i get rid of that?

The Subversion working copy. Revert.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: dev-help_at_subclipse.tigris.org