> Simply deleting the file from the working copy will not work--you must
> tell Subversion to remove it with 'svn rm'.
I anticipate there being more complex changes, where the user may not
necessarily know what needs to be deleted, moved, etc. Sorry, I should
have made that clear. I know about 'rm'.
What if a user makes many complex changes and wants to scrap them all,
and make the HEAD version look like an older revision with just a few
simple changes. Or for that matter, just make the HEAD revision look
exactly like an older revision.
Is this possible?
>
>
> On Sat, 19 Mar 2005 20:28:16 -0500, Mike Burr <meburr@gmail.com> wrote:
> > My apologies if this if this situation is addressed somewhere obvious.
> > I've read the FAQs and most of the "Version Control with Subversion".
> > Here's my situation, I have:
> >
> > Revision 1
> > file
> >
> > Revision 2
> > file
> > file2
> >
> > I would like to roll back to rev 1, make some changes (like add a
> > file3) and have:
> >
> > Revision 3
> > file
> > file3
> >
> > But what I find is that if I check out a new copy of 3, I have:
> >
> > Revision 3
> > file
> > file2
> > file3
> >
> > In other words, file2 sticks around, even though what I committed
> > (after a fresh checkout of rev 1) was only file and file3.
> >
> > Is there some other way of accomplishing this, or am I overlooking something?
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: users-help@subversion.tigris.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Mar 20 03:18:37 2005