Using iODBC Open Source Edition GIT Tree Introduction Developers who want to actively track progress of the iODBC source code and contribute bugfixes or enhancements to the project need Git access. This access requires basic knowledge of Git itself; the general layout of open source and GNU projects; the use of autoconf and automake; and other things that are beyond the scope of this document. Git Archive Server Access GitHub For main development, we publish the iODBC open-source tree to GitHub. We encourage everyone who is interested in tracking the project to create an account there. Users who mainly just want to look at the code can use the GitHub web interface or check out a local copy of the tree: $ git clone git://github.com/openlink/iODBC.git At this point, you can create your own work branch based on any available branch; create bug fixes; commit them to your own branch; and then use git format-patch to generate diffs. Developers are encouraged to fork the project on GitHub, create branches for enhancements and bug fixes, and submit pull requests so changes can be reviewed and incorporated into the main tree for future release. For more information, see GitHub Documentation. SourceForge OpenLink continues to use SourceForge to release source tarballs and certain binaries. SourceForge also contains a frozen CVS archive for historical reference, and read-only Git archive access is available there as well. For more information, see SourceForge Git Documentation. Git Tag-Signing Key To verify signed releases, import our Git public GPG key in one of these ways: Run: $ gpg --recv-keys 089DE67A Or download 089DE67A.asc and run: $ gpg --import 089DE67A.asc Or run: $ echo '-----BEGIN PGP PUBLIC KEY BLOCK----- mQENBE9pILIBCACpRFwsoYwyfswRt7QMWtifJb/L1Zo9955pKyOnnI/vZ2S2uFv0 OALpyUoR/WhQzIrtmzVYfBSmmBhAr5sh05tcXjFmyulhecAllYfaNAHEYAfgczaj 7TMYkHOd4xU2dl2PEPpWYaQJ/tuokZICC5BBakpHDN12TUrZTyCe1qEUgJvM6e3A 8BAwZSB9wbdwhxVwZEbeNYcINsBXL9kc/oy0v61XEIr17n/GS2Lmh533XP97kTz5 IJhTwrGf3lQUpEYRWptepUI2bnBSO3ZJ8G4x5w4ESP0f+Uw1ihx/yqTmOeeJfvX1 rhnLF5kOjN8xXtvI4nrYm/ctVtr68A33hjP9ABEBAAG0Q09wZW5MaW5rIFNvZnR3 YXJlIFNpZ25pbmcgS2V5IChHaXQgdGFncykgPGdpdC5hZG1pbkBvcGVubGlua3N3 LmNvbT6JAT4EEwECACgFAk9pILICGy8FCQeGH4AGCwkIBwMCBhUIAgkKCwQWAgMB Ah4BAheAAAoJEHtptnAIneZ6TJ8IAIytxv4t2umvjWFSOULLLTiQu11WMnYdPWS7 fMPVznZDpIs9RR1egmj4QAC0x/ImgtRGn3uoebNv2E9WBRYQw+OL4+AnY/y6Grfm plkOO/EW3GZYMMWjm6Ih7EhlLooW3Epv1oP8tdikVHKTPl4SiWSPOt1j+W1QyeFO 7EjWi1zSPL6R0kwqBY/Lpf2SXiiXU40FwoU2J2gPFcWYuBal1Jc3iiBq3hF9W5LZ kuJ0D09VXoS6hwc0GkEv2ibFmtBVOsjsjH6N3ENApLT5YK9Pgm2sk5kYXRLDsj1V 3ojRNFlZbFHr2Hwjwrh0vo9y5XeXUebMu+QPkIQmMeECFkcdl7Y= =zD+s -----END PGP PUBLIC KEY BLOCK----- ' | gpg --import The fingerprint of this key is 7D6E 3898 F670 9F7A C25C 19D0 7B69 B670 089D E67A. Further Documentation Please see our Git Usage document concerning the usage of branches and tags. For an introduction to Git, see the Git Quickstart and Tips guide.