Hillel,
> If patches are not accepted into CVS, kannel will stagnate and can't
> progress, so I'm sure those that have CVS access rights have a good reason
> why the patch has not gone into CVS yet.
I've been on these lists for some time now, and I'd say that the
guys are caught up in the midst of some major product. As such, they
probably find it hard to get the time -- even harder to get the energy
-- to read, review and commit patches. So on that note, things will
probably resume a more normal pace sooner or later.
> I do hope people still send in their patches, as even if the patches don't
> get into CVS, others can still learn from them.
The problem is that any changes which *are* committed threaten
externally maintained patches. This makes it very difficult to keep
your patch working against the latest CVS. It'd be nice if all
realistic patches could be committed -- possibly with design, code or
theory changes -- to the main source tree. This has always been hard
for major patches -- even harder lately (as mentioned above), even for
the little patches.
Jon
