FreeTDS Development Group

[James K. Lowden <jklowden AT speakeasy.org>]

On Mon, 16 Sep 2002 18:31:37 -0400, "Andrea Spinelli"
<aspinelli AT imteam.it> wrote:
> I have worked a bit around src/odbc.c, and I
> have added support for commit/rollback,
> autocommit on/off, a bit more support for
> SQL_TIMESTAMP, a fix for SQLStmtFreeHandle,
> a fix for SQLGetTypeInfo.

An especially warm welcome to you, Andrea!  You bring exceedingly good
tidings.  

You didn't mention what version of the source you were working from.  The
more recent it was, the easier merging in your helpful additions will be. 


> How can I help?  I am not a CVS expert,
> but of course I can learn...

What we'd like best, if you can, is the output of "diff -u".  I for one
find it easier to understand the impact of a patch by looking at diff(1)
output than anything else.  If you worked from a recent snapshot, you can
just run 

        "diff -u snapshot yourfile > file.diff"  

and post the output to SourceForge.  Frediano will probably want to have a
look at it, because he's been doing a lot with ODBC.  

If you were working with 0.53, your changes will be quite difficult to
merge in, I imagine.  In that event, you'll probably want to merge your
code into the current sources yourself.  It will be much easier for you as
the author than for any of the maintainers.  

CVS.   I'll start from the beginning.  Please skip what's obvious.  

You should have a cvs client installed on your machine (most OSes come
with one or make it easy to add).  

Follow the directions on the SourceForge site for cvs access. 

        http://sourceforge.net/cvs/?group_id=33106

(Hint: "modulename" is "freetds".) 

That will give you FreeTDS's current source tree.  

Merge in your changes, compile until happy.  When you're ready, 

        cvs diff -u freetds >freetds.diff  

and post the patch.  Patches posted to sf trigger notification to the
list.  

Hope that's clear and useful.  

Regards, 

--jkl