Re: what's the latest on sms_client?

Andrew Lowe <[email protected]> Wed, 11 Aug 2004 09:46:35 +1000
Newsgroups gmane.comp.mobile.sms.tsms
Message-ID <[email protected]>
This is a multi-part message in MIME format.
--===============89121160511549991==
Content-Type: multipart/alternative;
	boundary="------------040108020600060203090000"

This is a multi-part message in MIME format.
--------------040108020600060203090000
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Per Jessen wrote:

>2. I noticed the last release is a tad old - I guess there isn't much activity
>on the development front? 
>
>  
>
I too have noticed this, however there does not appear to be much 
needed, when all bugs are fixed and there are no more feature requests, 
I guess you don't need any more development.

I think the maintainer was going to release a new version soon, mainly 
just updating service details.

>3. I am missing an option to set the originator-number on a message - I managed
>to hack ucp.c, but where do I send patches?
>  
>
 From the FAQ (http://www.smsclient.org/faq.php):

    <>/ Question  / How do I send patches?/
    Answer /

    If the patch is not too big you can send them to the mailing list.
    Otherwise just put them online and mail the url. It's a good thing
    (TM) to save some bandwith.

Also the Download site (http://www.smsclient.org/download.php) has the 
current maintainer contact details, however with the current state of 
development it would probably be best to send the patch to the mailing 
list so that everyone can use it now if they want to.
-- 

Andrew Lowe
    System Administrator & Programmer
        Information Technology
            Manildra Group

Email:   [email protected]


--------------040108020600060203090000
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
Per Jessen wrote:
<blockquote cite="[email protected]" type="cite">
  <pre wrap="">2. I noticed the last release is a tad old - I guess there isn't much activity
on the development front? 

  </pre>
</blockquote>
I too have noticed this, however there does not appear to be much
needed, when all bugs are fixed and there are no more feature requests,
I guess you don't need any more development.<br>
<br>
I think the maintainer was going to release a new version soon, mainly
just updating service details.<br>
<br>
<blockquote cite="[email protected]" type="cite">
  <pre wrap="">3. I am missing an option to set the originator-number on a message - I managed
to hack ucp.c, but where do I send patches?
  </pre>
</blockquote>
>From the FAQ (<a class="moz-txt-link-freetext" href="http://www.smsclient.org/faq.php">http://www.smsclient.org/faq.php</a>):<br>
<br>
<blockquote>
  <dl>
    <><em class="question"> Question &nbsp;</em> How do I send patches?<em
 class="answer"><br>
Answer </em>
    <p> If the patch is not too
big you can send them to the mailing list. Otherwise just put them
online and mail the url. It's a good thing (TM) to save some bandwith.</p>
    </>
  </dl>
</blockquote>
Also the Download site (<a class="moz-txt-link-freetext" href="http://www.smsclient.org/download.php">http://www.smsclient.org/download.php</a>) has the
current maintainer contact details, however with the current state of
development it would probably be best to send the patch to the mailing
list so that everyone can use it now if they want to.<br>
-- <br>
<pre class="moz-signature" cols="72">
Andrew Lowe
    System Administrator &amp; Programmer
        Information Technology
            Manildra Group

Email:   <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a></pre>
</body>
</html>

--------------040108020600060203090000--


--===============89121160511549991==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--

-----------------------------------------------------------------------