You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Karl Fogel <kf...@galois.collab.net> on 2001/02/13 22:28:13 UTC

fs progress, and question for JimB/Branko

Yay Jim!  Those are some meaty commits I see coming down the wire. :-)
Branko too.  The fs is really moving... <purr>

I too am feeling joyful in the filesystem lately (my commits may not
be as big, sniff, but remember, happiness cannot be gauged in bytes.)
Today was dag.c:svn_fs__dag_clone_root, and the new code depends on
the as-yet-unimplemented functions

   svn_fs__get_node_revision()
   svn_fs__create_successor()

which are in rep.c, which is commented out of the build temporarily,
due to interface changes.

So I'm thinking my next step will be to make rep.c work again, with
the above two functions first priority.

Should it come back as node-rev.c, or should node-rev.h become rep.c?
(The interface currently exported by node-rev.h seems to be
implemented in rep.c.)

-K

Re: fs progress, and question for JimB/Branko

Posted by Jim Blandy <ji...@zwingli.cygnus.com>.
Karl Fogel <kf...@galois.ch.collab.net> writes:
> Yay Jim!  Those are some meaty commits I see coming down the wire. :-)
> Branko too.  The fs is really moving... <purr>
> 
> I too am feeling joyful in the filesystem lately (my commits may not
> be as big, sniff, but remember, happiness cannot be gauged in bytes.)
> Today was dag.c:svn_fs__dag_clone_root, and the new code depends on
> the as-yet-unimplemented functions
> 
>    svn_fs__get_node_revision()
>    svn_fs__create_successor()
> 
> which are in rep.c, which is commented out of the build temporarily,
> due to interface changes.
> 
> So I'm thinking my next step will be to make rep.c work again, with
> the above two functions first priority.
> 
> Should it come back as node-rev.c, or should node-rev.h become rep.c?
> (The interface currently exported by node-rev.h seems to be
> implemented in rep.c.)

Just move the code over into node-rev.c.  "rep" suggests
"representation", but while the module *works* with representations,
its job is to provide an interface which deals with node revisions, so
node-rev is a better name.