Re: storing URLs in SVN/

Greg Stein <gstein@lyra.org> writes:
> And since it is hard-coded, it is kind of hard to tell which/how that string
> is getting in there. ./SVN/entries looks like:
>
> ...
> <entry
> name="subsub"
> kind="dir"
> ancestor="### ancestor_path ###/subsub"/>
> ...
>
> And subsub/SVN/entries has:
>
> ...
> <entry
> name=""
> kind="dir"
> revision="1"
> ancestor="### ancestor_path ###"/>
> ...

The first entry shouldn't have an ancestor field. It's a bug. :-)

But in general, it shouldn't matter to you what the files look like.
Your interface is programmatic, function-based not file-based.

> This goes back to whether ancestor_path / ancestor_revision should be passed
> during a checkout. I think "no" (but I have to set them today, or the WC
> chokes during the checkout). The path is built from NAME, and the revision
> should be passed thru something like a set_revision() editor callback.

Huh? I don't see how it goes back to that.

There are now so many issues flying around that I am officially lost.
See you tomorrow. :-)

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