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

Re: Alpha issues [or "How to Organize Your Weekend" :-) ]

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-07-11 23:37:44 CEST

> > 751: need an svn-config file
> > ==> Ben and I are planning to take a look at this tomorrow. BUT,
> > if someone wants to do this, go for it! Just take a look at
> > apu-config for example, and post with questions. We'd love
> > to be able to concentrate on issue #494 and friends :-).
>
> I can do this.

Awesome, thanks! I saw the other followups on this thread, and assume
you did too. As soon as Issuezilla is showing bugs again (it's
experiencing bad weather at the moment) I'll assign this one over to
you.

Also, folks, there's one other issue that could be fixed in Alpha, if
someone wants to take it on:

   http://subversion.tigris.org/issues/show_bug.cgi?id=611

Note that there are two parts to this issue. The first part is kind
of complex -- it's about how when you "svn mv A A2" (where A is a
versioned directory), a skeletal A tree is left around afterwards.
This is a side effect of the fact that "mv" is really "svn cp A A2;
svn rm A". The problem is that "svn rm" wants to leave around A's
tree, with all the .svn subdirs and text bases, so that "svn revert"
will work later. Of course, it doesn't know that it could get all
that stuff from A2 if it had to.

Solving this first part of the bug is too complex for Alpha. In fact
it's debatable that it needs to be solved at all, since you could have
done

   $ svn mv ./A ../../A2
   $ svn revert --recursive .

and it can get really hard to revert this stuff unless the base tree
is still around.

However, the *second* part of the issue is very simple: it's that even
after you commit the removal, the old tree stays around in skeleton
form. Solving this is pretty non-controversial -- the old tree should
simply get removed, except for paths down to local mods. Philip
Martin has some more comments in the issue, see there for details.

Why is this a potential Alpha fix?

Ben Collins-Sussman pointed out that directory versioning is our big
selling point, so everyone who sees we're at Alpha and downloads SVN
for the first time will want to play around with "svn cp" and "svn
mv", on both files and directories. It would be a pity (though not an
insurmountable pity) if things behaved wierdly for them -- for
example, the SRC tree of "svn mv SRC DST" remaining in their working
copy even *after* they commit :-).

So it would be nice if someone wanted to try swatting the post-commit
bug here.

If not, no big deal, we'll just list the misbehavior on our
Inconveniences Page and do it for Beta.

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 11 23:48:47 2002

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

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