[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Replace with History?

From: Eric Berry <elberry_at_gmail.com>
Date: 2007-06-14 21:55:26 CEST

Hi Mark and Russ,

> That would be the best way to undo the change. I think what the O.P.
> said was that they successfully undid the change, but now wanted it
> back. I imagine they committed something that was not ready but which
> they ultimately want to commit.

This is exactly the case. I actually had a directory that needs to be
committed, but a branch needed to be created first. I realize now that
I could probably have just created the branch using the revision
number just before I committed that directory.

However, I successfully removed the directory and committed the
removal which removed the directory and it's files from the repository
and my local working copy.

I then wanted to retrieve the directory and files from the repository
so that I could have them in my local working copy, so I could
recommit them at a later date, after the branch had been cut.

Mark, I tried to do the show history on the directory and then get the
contents, but I was not able to. I'm guessing that this feature only
works on files themselves.

> If this was a big change, they could use merge to re-apply the
> revision of the original commit.

Can you help me with this a little. I think this will be the best way
for me. I've right clicked on the directory and chosen "merge". When I
take the revision just before the removal (to), and the head (from). I
get my files back, but their file names are surrounded by the '#'
symbol now. I don't think I did this right, what did I do wrong?


Learn from the past. Live in the present. Plan for the future.
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Jun 14 21:55:47 2007

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.