hamlib-cvs-digest — hamlib commit digest

[Hamlib-cvs-digest] CVS: hamlib/src Makefile.am,1.2,1.3

[Stephane F. <f4...@us...>]

Update of /cvsroot/hamlib/hamlib/src
In directory slayer.i.sourceforge.net:/tmp/cvs-serv27374

Modified Files:
	Makefile.am 
Log Message:
* Listed local include files

Index: Makefile.am
===================================================================
RCS file: /cvsroot/hamlib/hamlib/src/Makefile.am,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -r1.2 -r1.3
*** Makefile.am	2000/10/08 21:41:54	1.2
--- Makefile.am	2000/10/16 21:50:33	1.3
***************
*** 3,4 ****
--- 3,5 ----
  lib_LIBRARIES = libhamlib.a
  libhamlib_a_SOURCES = rig.c serial.c misc.c register.c event.c
+ noinst_HEADERS = event.h misc.h serial.h

[Hamlib-cvs-digest] CVS: hamlib/include/hamlib riglist.h,1.2,1.3

[Stephane F. <f4...@us...>]

Update of /cvsroot/hamlib/hamlib/include/hamlib
In directory slayer.i.sourceforge.net:/tmp/cvs-serv27096

Modified Files:
	riglist.h 
Log Message:
* Added RIG_MODEL_MINISCOUT


Index: riglist.h
===================================================================
RCS file: /cvsroot/hamlib/hamlib/include/hamlib/riglist.h,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -r1.2 -r1.3
*** riglist.h	2000/10/10 22:05:23	1.2
--- riglist.h	2000/10/16 21:48:48	1.3
***************
*** 83,87 ****
  	RIG_MODEL_ICR8500,
  	RIG_MODEL_ICR9000,
! 	RIG_MODEL_PCR1000
  
  	/* etc. */
--- 83,88 ----
  	RIG_MODEL_ICR8500,
  	RIG_MODEL_ICR9000,
! 	RIG_MODEL_PCR1000,
! 	RIG_MODEL_MINISCOUT
  
  	/* etc. */

[Hamlib-cvs-digest] CVS: hamlib/ft747 ft747.c,1.17,1.18

[Frank S. <jav...@us...>]

Update of /cvsroot/hamlib/hamlib/ft747
In directory slayer.i.sourceforge.net:/tmp/cvs-serv5419

Modified Files:
	ft747.c 
Log Message:
minor fixes


Index: ft747.c
===================================================================
RCS file: /cvsroot/hamlib/hamlib/ft747/ft747.c,v
retrieving revision 1.17
retrieving revision 1.18
diff -C2 -r1.17 -r1.18
*** ft747.c	2000/10/09 01:17:19	1.17
--- ft747.c	2000/10/14 03:55:26	1.18
***************
*** 27,34 ****
   */
  
- 
- 
- 
- 
  #include <stdlib.h>
  #include <stdio.h>   /* Standard input/output definitions */
--- 27,30 ----
***************
*** 635,645 ****
   * init_ft747 is called by rig_backend_load
   */
! int init_ft747(void *be_handle)
! {
! 		rig_debug(RIG_DEBUG_VERBOSE, "ft747: _init called\n");
! 
! 		rig_register(&ft747_caps);
! 
! 		return RIG_OK;
  }
  
--- 631,638 ----
   * init_ft747 is called by rig_backend_load
   */
! int init_ft747(void *be_handle) {
!   rig_debug(RIG_DEBUG_VERBOSE, "ft747: _init called\n");
!   rig_register(&ft747_caps); 
!   return RIG_OK;
  }
  

[Hamlib-cvs-digest] Re: [Hamlib-developer] CVS Updates via email

[Frank S. <vk...@ix...>]

Frank Singleton wrote:

> 
> I have  added syncmail to CVSROOT and sent a request to
> have it activated.

Done

> 
> Should be up in 48 hrs hopefully.
> I need to configure a few things once the sourceforge
> lads have activated it for me.
> 
Done

> Then we will have some
> "very pretty" automatic cvs emails indeed :-)

Well its up and running!! I updated TODO as a test, and
the email automagically came as expected 
to ham...@li...

Note: Its more efficient if you have a daily
digest instead of 1 mail per update when you
receive the emails. This is set in your "email
preferences " on the hamlib site.

ie: "Set Digest Mode" 


Enjoy / Frank.. :)

-- 
Frank Singleton				VK3FCS

Email: victor kilo three foxtrot charlie sierra at ix dot netcom dot com

[Hamlib-cvs-digest] CVS: hamlib TODO,1.9,1.10

[Frank S. <jav...@us...>]

Update of /cvsroot/hamlib/hamlib
In directory slayer.i.sourceforge.net:/tmp/cvs-serv17890

Modified Files:
	TODO 
Log Message:
cvs mail update works ok :-)


Index: TODO
===================================================================
RCS file: /cvsroot/hamlib/hamlib/TODO,v
retrieving revision 1.9
retrieving revision 1.10
diff -C2 -r1.9 -r1.10
*** TODO	2000/10/12 17:47:49	1.9
--- TODO	2000/10/12 18:37:56	1.10
***************
*** 33,37 ****
  17. In serial.c (and non serial too), use buffered IO instead of read/write,
  	for better performance. Use flushing with fwrite.
- 18. Get CVS updates mailed to out hamlib-cvs-digest list
  
  DONE
--- 33,36 ----
***************
*** 40,42 ****
--- 39,43 ----
  9. If read from rig takes > "n" seconds, then no longer
     block on read, just return error. 
+ 
+ 18. Get CVS updates mailed to our hamlib-cvs-digest list
  

[Hamlib-cvs-digest] CVS: hamlib TODO,1.8,1.9

[Frank S. <jav...@us...>]

Update of /cvsroot/hamlib/hamlib
In directory slayer.i.sourceforge.net:/tmp/cvs-serv29777

Modified Files:
	TODO 
Log Message:
cvs mails to hamlib-cvs-digest


Index: TODO
===================================================================
RCS file: /cvsroot/hamlib/hamlib/TODO,v
retrieving revision 1.8
retrieving revision 1.9
diff -C2 -r1.8 -r1.9
*** TODO	2000/10/01 14:31:31	1.8
--- TODO	2000/10/12 17:47:49	1.9
***************
*** 33,36 ****
--- 33,37 ----
  17. In serial.c (and non serial too), use buffered IO instead of read/write,
  	for better performance. Use flushing with fwrite.
+ 18. Get CVS updates mailed to out hamlib-cvs-digest list
  
  DONE

[Hamlib-cvs-digest] CVS Updates via email

[Frank S. <vk...@ix...>]

> From: Stephane Fillod <f4...@fr...>
> To: ham...@li...
> Subject: [Hamlib-cvs-digest] automatic Hamlib-cvs-digest?
> 
> Frank,
> 
> Your commit reports are great, 

<blush>

>I'm wondering if I would have the time
> to do as well each time I commit. Anyway, I was more expecting this
> mailing list to *automatically* post the -m messages of the commits
> of the day.
> 
> Is it possible? Or is it something we have to add in a space cron tab
> with a script of ours?
> "Your asking the moon, please hold on...."
> 
> Cheers,
> 
> --
> Stephane                                        F4CFE

Hi hamlib crew,

Yeah this is a cross-post, but it affects us all ;-)

I have  added syncmail to CVSROOT and sent a request to
have it activated. 

Should be up in 48 hrs hopefully.
I need to configure a few things once the sourceforge
lads have activated it for me.

Then we will have some 
"very pretty" automatic cvs emails indeed :-)

Cheers..

-- 
Frank Singleton				VK3FCS

Email: victor kilo three foxtrot charlie sierra at ix dot netcom dot com

[Hamlib-cvs-digest] automatic Hamlib-cvs-digest?

[Stephane F. <f4...@fr...>]

Frank,

Your commit reports are great, I'm wondering if I would have the time
to do as well each time I commit. Anyway, I was more expecting this
mailing list to *automatically* post the -m messages of the commits
of the day. 

Is it possible? Or is it something we have to add in a space cron tab
with a script of ours? 
"Your asking the moon, please hold on...."

Cheers,

-- 
Stephane					F4CFE

[Hamlib-cvs-digest] Minor update

[Frank S. <vk...@ix...>]

Hi,

General
-------

Added post_write_delay to write_block(), to cater for rigs
that cannot handle fast sequential writes without a
delay.


Files
-----

Affected all files with references to write_block, and  rig_caps
structures. Non yaesu rigs had "0" inserted as post_write_delay .
Yaesu rigs start had "5msec" setting inserted.

CVS tree compiles and tests ok.

/Frank..

-- 
Frank Singleton				VK3FCS

Email: victor kilo three foxtrot charlie sierra at ix dot netcom dot com

[Hamlib-cvs-digest] Welcome to hamlib-cvs-digest

[Frank S. <vk...@ix...>]

Hi,

Welcome to the hamlib-cvs-digest mail list.

The main purpose of this list is to allow developers and
others of the hamlib libraries to document/commment
on CVS submits to the project.

This allows one to see what has been happening with
the CVS tree. This can assist greatly when you suddenly find
perhaps something no longers compiles properly, or there
has been an API change etc..

The submissions should provide a quick summary of what has changed,
and then a short summary for each file affected.

In order for others to understand the changes,
I propose the format of the submissions should be as follows.

Here is an example..

<snip>

Hi,


Summary
-------

Allow more options for serial speed selection
and more examples  of rig_set/get.

testrig.c
--------

Added 2 more examples of set/get

retcode = rig_set_mode(my_rig, RIG_MODE_FM);
retcode = rig_get_mode(my_rig, &rmode);

serial.c
--------

Added 9600 bps as a possible speed selection.

<snip>


Look forward to lots of useful submissions :-)


/Frank.

73's de vk3fcs/km5ws

-- 


Frank Singleton				VK3FCS

Email: victor kilo three foxtrot charlie sierra at ix dot netcom dot com