The GnuPG development is tracked using the GIT distributed revision control system. A public read-only GIT repository for GnuPG and related projects is available.

This service is provided to help you in hunting bugs and not to deliver stable snapshots; it may happen that it even does not compile, so please don't complain. GIT may put a high load on a server, so please don't poll for new pushes too often. Instead, we suggest you to subscribe to the commits mailing list .

You may also follow @gnuprivacyguard on Twitter to get notified about commits to the GnuPG master branch.

There is a Web interface at https://git.gnupg.org/ which can be used to browse the GIT repository.

All repositories have been migrated to GIT from the old Subversion (SVN) code management tool. The standard way you checkout from an anonymous GIT is to clone the entire repository from one of these repositories:

git clone https://dev.gnupg.org/source/gnupg.git
git clone git://git.gnupg.org/gnupg.git

You must run ./autogen.sh before running the ./configure in the way suggested by the output of autogen.sh. This creates some required files which are not stored in the repository. autogen.sh also checks that you have all required tools installed. Please read the GIT manual pages before doing so. The current development version is 2.3.8 and known as STABLE-BRANCH-2-4; the long term support (LTS) version is 2.2.40 and known as STABLE-BRANCH-2-2; the legacy 1.4 version of GnuPG (1.4.23) is known as STABLE-BRANCH-1-4.

Bug reports should go to the developers mailing list. See the page on mailing lists .

The GnuPG Git server also hosts some other projects in Git repositories. Please use the web interface at https://git.gnupg.org/ to browse them.