I got no comment on this issue:

>   -- the program does a linear scan of the commit log,
>      so in the long term, we can have problems.
>      I would like to have each log message saved in
>      a file in some sort of directory structure
>      (I was considering:
>        commitlog.d/<year>/<week of year>/<id of msg>)
>      That would be much better and I would be happy
>      to implement it if no one objects to it.

Should I implement this, or we should we stick with the
big commit log file? The nice thing about the above
solution is that, if the msg ids are in increasing order,
we can generate the big log file with:

cat commitlog.d/*/*/*

so I like it a lot more than the one file solution.

Comments?

--
Dimi.


Reply via email to