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

Re: ancestor path / revision

From: Karl Fogel <kfogel_at_galois.collab.net>
Date: 2000-12-19 19:47:18 CET

Ben Collins-Sussman <sussman@newton.collab.net> writes:
> So it's critical that the working copy know the absolute locations of
> every resource it manages. During a commit, it needs to say *exacly*
> which resource is being changes. And during a pre-update "report", it
> needs to say exactly which resources it has. Any time the working
> copy ever speaks to the repository, it must speak in absolute paths
> and revision numbers.
>
> Thus when receiving a first-time checkout, this info needs to be given
> to the working copy. The working copy can't function without it. Any
> other system implies that the repository needs to keep track of every
> working copy in existence, which is *not* our model. :)

Well, yes, but:

That doesn't mean the checkout editor needs to receive an
`ancestor_path' argument in every call. It only needs it in the
replace_root() call, and then it can construct the rest by using
svn_path_append() and the `name' arguments, as it goes.

Yes, the ancestry information has to be present, when all is said and
done and the working copy is checked out. But how you got the
information is another matter.

-K
Received on Sat Oct 21 14:36:17 2006

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