>I implemented everything on the v1001 tag. I have pulled the latest in
>git and am creating a local branch with my updates. Should I commit
>the code to master after I finish testing?
I have this annoying habit of going through code and doing syntax and style
cleanup when I am attending boring meetings at work but can't commit to focusing
on real development. The result is that if you have a patch it might not
apply cleanly because it might be against code where I changed "return(1);"
to "return 1;" or something silly like that.
I'll stop doing that now that I know you have stuff coming in. Please sync
up with git master and then if everything is working then yes, it would be
easiest if you could just commit to the main line. Please PM me with your
desired username and password because we're not using GitLab-CE anymore --
it was just consuming too many resources
so I switched back to regular `git` with the `cgit` web front end. So when
we create your account it'll just be an ordinary account on the server with
permission to write to the repository.
It sounds like we're in agreement on what it has to do:
* The server must be able to read records in old or new format
* The server will always write in the new format
* ctdldump must be able to read in old or new format, but always dumps in
new format
* ctdlload understands the new format only
I like what you're doing. The purpose of the 'visit' record is to identify
the relationship between a user and a room, and with these extensions it will
more clearly identify the relationship between a user and messages within
the room. As the Citadel System evolves, the concept of a "room" will begin
to fade for users on the web UI, but it will still be the primary internal
representation. So the more flexibility we have, the more useful it will
be.
