On Tue, Nov 28, 2000 at 01:44:28AM -0600, Ben Collins-Sussman wrote:
> Greg Stein <gstein@lyra.org> writes:
>...
> > I think it also needs one when it is updating.
> >
> > crawler_editor => ra_editor => wc_editor
> >
> > "crawler finds an reports items to RA which fetches updates which
> > applies them via WC"
>
> Right.
>
> Right now, adm_crawler.c is a program that recursively walks the
> working copy and reports local mods to an editor; it's the essence of
> the `commit` command. But I need to write a smaller version of this
> program. Specifically, one which notices nothing but revision
> numbers; it reports an object to the editor iff the objects' revision
> number is different than a particular "base" revision. This is
> essentially our `skelta' idea from way back when.
>
> So ra will need to make two editors available for driving: one for
> reporting a skelta to the repository, and one for committing.
Why? I don't understand what the first step is accomplishing. Are you
talking about doing a "preflight" to see if the all of the changed files are
current or something?
But we took care of that with the postfix delta. We can walk the tree,
fetch version numbers and compare them, and after all that, then we upload
the actual changes and commit them.
Why two steps?
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:15 2006