From: Jens Rehsack <jr_extern@vfnet.de>
To: ofono@ofono.org
Subject: Re: New test scripts ...
Date: Wed, 27 Jun 2012 12:15:29 +0200 [thread overview]
Message-ID: <4FEADD41.3000307@vfnet.de> (raw)
In-Reply-To: <1340722566.29898.27.camel@aeonflux>
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
On 26.06.2012 16:56, Marcel Holtmann wrote:
> Hi Jens,
Hi Marcel,
>> for personal requirements (debugging) I added 3 simple scripts
>> (attached) to dump the properties of specific modem interfaces.
>>
>> Shall I send patches for them or are they useless for the project?
>> (For the records: I don't mind either)
>
> sending patches would be better. Especially since you might wanna have
> them added to Makefile.am as well.
I just wanted to know if it's worth (for them and for future),
... scheduling prepare the patches
> As a note, have you considered creating one script with different
> command line options? Our script collection is getting kinda big ;)
No, I didn't - to keep it easy (and I don't know how to do that
in Python). For universal access with CLI I'd blow up the announced
Net::Radio::oFono Perl5 module :)
Best regards,
Jens
prev parent reply other threads:[~2012-06-27 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 9:24 New test scripts Jens Rehsack
2012-06-26 14:56 ` Marcel Holtmann
2012-06-27 10:15 ` Jens Rehsack [this message]
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FEADD41.3000307@vfnet.de \
--to=jr_extern@vfnet.de \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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