From: Bengt Kleberg <firstname.lastname@example.org>
To: email@example.com, firstname.lastname@example.org
Subject: Re: Samx - one more time ...
Date: Tue, 25 Apr 2000 10:38:51 -0400 [thread overview]
Message-ID: <200004251438.QAA08798@trillian.softwell.se> (raw)
> I worry that I might be "splintering" sam
I am (very low-key) maintaining sam as it is, just doing bug fixes and adding
ports \x19(ie making sure that configure works for any new platforms).
Sometime in the future, if time permits, I will try to remove any hardcoded limits
(like the 512 characters samterm -> sam message limit).
I will not attempt to add features.
You have clearly a much broader scoop in your interest for sam.
Perhaps we complement each other? I maintain sam as it is, you enhance it?
Effectivly creating two sams, ofcourse. Presumably sam-as-it-is will stop beeing
used, and that does not matter to me since I am not doing anyhting anyway.
However, have you looked at wily? This is generally considered as a alternative to sam,
and it has loads of the things you seem (to me) to be interested in. Perhaps it would be better
to devout your energy to wily instead?
Best Wishes, Bengt
Everything aforementioned should be regarded as totally private
opinions, and nothing else. email@example.com
``His great strength is that he is uncompromising. It would make
him physically ill to think of programming in C++.''
next reply other threads:[~2000-04-26 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-25 14:38 Bengt Kleberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-27 20:17 Russ Cox
2000-04-27 8:04 Bengt Kleberg
2000-04-26 22:34 Paul Jackson
2000-04-26 22:26 Paul Jackson
2000-04-26 20:25 Paul Jackson
2000-04-25 12:42 rob pike
2000-04-21 2:08 Paul Jackson
2000-04-25 10:59 ` Alex Danilo
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).