>>>> "Ben" == Ben Wing
Ben> i guess what i mean is, google automatically threads,
etc, etc. I don't think either Gnus or VM does what you want. Both
automatically thread, but both sort threads by oldest visible message
in thread by default. In VM that may mean unread-only, but gnus
allows you to flag the message.
The other stuff I don't think they do; I'll have to take a look at gmail.
Ben> btw you complained about cvs; everyone i know seems to be
Ben> moving to subversion. any thoughts? i think you looked into
Ben> this quite a lot, but this might have been awhile ago.
I've used subversion a bit with a couple of other projects.
Subversion seems to be a much better CVS, exactly as billed. AFAICT
it will not help with the megapatch problem, it will not help with
intelligently merging multiple related workspaces, but it would be
much more robust in day-to-day work.
Of the "modern RCSes", I've tried Arch, Darcs, and git. The first two
are not competitive with subversion or CVS for speed, even though most
of their work is done locally, not over the net. git is a great tool
for intelligent merging. Unlike Arch and Darcs, it doesn't try to be
intelligent, but it's so fast and reliable that you can use *your*
intelligence to sort out the likely conflicts, and you can afford to
try a merge and throw it away if it didn't work. It also cooperates
well with smerge.el and diff-mode.el.
git doesn't seem to mind having other RCSes update behind its back.
Bottom line is I no longer really care what the project uses, and
probably don't need to. I don't work at the scale that you do, but
Linus and Co do, and I'm pretty confident that git will scale with
whatever you throw at me.
I don't yet really have it systematically set up, either. It really
needs menu-based cherry-picking and a darcs-like hunk-by-hunk commit
selector, but even so, I can't imagine life without it any more.
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.