Contributions to mincrypt

(aka mincrypt hacking)

Hacking mincrypt

If you want to implement new features to mincrypt or fix some bugs you have found you can download the source from our GIT repository using

git clone git://github.com/MigNov/minCrypt.git

Please make sure you're using the coding style in which the code is already written (beware of spaces instead of tabs etc). When you have the patch prepared please send us the patch using the procedure mentioned in Sending patches paragraph.

Sending patches

If you would like to contribute to the libvirt-php project you could write patches for it but please make sure you're following the procedure below:

  1. Set your git username and e-mail and also set the subject prefix in the project's repository using: 
    git config --local format.subjectprefix "mincrypt"
  2. Create the patch in the form of the commits and include also information about usage (example source codes maybe) and testing
  3. Format it using git format-patch -X where X is the number of patch parts to be posted, for multipart patch (X is greater than 1) please use also numbering (-n) option and include the cover-letter (--cover-letter).
  4. Send to my e-mail address mignov@gmail.com using your favourite e-mail client and prepend the mincrypt: prefix to the e-mail. Since my private e-mail account is being hosted on Gmail the git send-email <files> --to mignov@gmail.com command won't most likely work because gmail policy. <files> stands for 000*, i.e. all the patches formatted by git format-patch since git format-patch names the files starting with the 4 digit numbers.