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

[TSVN] Ignoring a commit and moving on

From: Gary Affonso <glists_at_greywether.com>
Date: 2005-02-26 01:13:26 CET

I've got version 75 of my repository to which I've been making local
(working copy) changes.

Another developer has just committed 76 and 77, both of which I just want to
throwaway. They contain problem code that's way easier to just ignore (and
start over) than to try and merge.

But I can't commit my latest working changes until I update to the latest
head (77) which I do not want to do.

So...

Is there a way to, in essence, ignore the fact that commits 76 and 76 ever
happened? Or delete them? Or commit "around them"? Or something?

Any suggestions for how to handle this situation are greatly appreciated.

Thanks,

- Gary

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Feb 26 01:13:59 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

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