Source code

Source code

Version control with Git

OpenSC source code is managed with Git. The history of OpenSC source code versioning is from None → CVS → SVN → Git. As the transitions have been done with automatic tools (cvs2svn, git-svn) some “corners” might be incorrect but the overall linear history of source code should be recognized and “git blame” should work as expected.

Master repository is hosted on Github: https://github.com/OpenSC/OpenSC/

Getting the source code

git clone git://github.com/OpenSC/OpenSC.git
cd OpenSC

Individual developers also have their own Github trees, Nightly Builds lists ones that you can get binaries from and Get Involved lists all known active developers.

Source code style and recommendations

Head to Development Policy for now.

Sending patches

First, please read DevelopmentPolicy for tips on how to prepare your patch and the commit message. Be prepared to re-work your patch based on feedback. All patches go through review and you can alos help doing Code Review.

If you have forked on Github

• Please open pull requests against staging branch
• Do NOT send pulls requests containing merge commits (at the moment at least, needs discussion)

Via mailing list or Trac

• Prepare your patches (assuming, that you forked/cloned the repository and started your feature branch with git checkout -b mychanges master. NB! Always include the link to the ticket in commit message!
• git format-patch master..HEAD
• Send the generated 00XX-patch-description.patch} files to opensc-devel mailing list
• If you have a patch that fixes a ticket, you could also attach it to the relevant ticket