you want to use emacs' -*- outline -*- mode, to read this ...

this file is some kind of TODO file, I use it to take down notes, what to
do, when and how ...

* first things first
** you're welcome to participate in progressing cvsfs
   if you got questions concerning it, don't hesitate but send me
   a mail to stesie@brokenpipe.de

** cvsfs' code is real crap!
*** do you think so? please tell me what you don't like
    cvsfs is actually my first project, related to the
    Hurd and actually my first step towards OS-near programming.

** cvs_*.[ch] files should stay GNU Hurd independant
   that is, please use POSIX compatible code in those files to keep those
   portable. The other stuff (cvsfs.c, node.c, netfs.c at the time of this
   writing) is OS (aka Hurd) specific and probably needs to completely be
   rewritten when aiming to port to some other platform.

** source code documentation
   all functions in all of cvsfs's files should be well documented,
   this unfortunately isn't the case currently.  if you want to, you may
   supply some however.  when implementing new stuff, just write it first,
   so that won't happen in future ;)

* todos
** available stuff left to fix
*** urgent
**** expire revision contents to disk
     keep revision's content until translator's exit somewhere below /tmp
     with rather strict umask applied.

     is this really clever??  I am not too sure, we can leave it to the
     pager to get rid of old revisions, we don't need anymore ...

*** things that can wait

** new features
   these are somewhat in order of urgency ...

*** support subversion as an alternate backend

*** display a list of available branches and tags

*** make loginfo accessible some way
    (<filenode>/history or something)

*** allow revision access like Linux' cvsfs does
    (using @@ appendixes)


jupp, enough for the time being ...
$Id: HACKING,v 1.9 2005/11/16 21:18:08 stesie Exp $