From ADC

Prev

Up

Your help wanted!

There is no specific requirements for supplied patches. Context diffs are preferred.

Good descripition raises chances, that we catch the idea of the patch. When writing a descripition, don't explain what changes the patch introduces. It can be seen in the patch itself. Try to cover what it is good for, or what problems it solves.

Contents 1 Choosing topic 2 Working with code 3 Submitting patches

Choosing topic

Most outstanding topics are formulated as issues in abstract/features component in issue tracker. Feel free to contact project administrator if you need more information.

Working with code

If you serioulsy plan to track and contribute to abstract, you should consider getting acquainted with git. Please see Build#Git Clone on getting a clone of abstract repository.

Git is specifically designed for distributed development of free software. It is just what we are doing. Git is not checking out a version or revision, it clones a comlete repository. Each git repository is self sufficient. You need network connection only to query for updates or to submit your work. All other tasks are done autonomously. Git is times or even orders of magnitude faster than competing SCM products on most tasks.

Here is an example of workflow for creating a patch series with git:

Clone a copy of git repository

   git-clone git://repo.or.cz/abstract.git

Change to your copy

   cd abstract

Run test suit

  ./check.mk

Create your topic branch

  git-checkout -b topic

Do some work, run test suit, save your changes. Repeat until you are ready to submit

  edit ...
  ./check.mk
  git-add ...
  git-commit
  ...

Create temporary directory for exported patches

  mkdir /var/tmp/out

Generate patches

  git-format-patch -o /var/tmp/out -n -s --thread master..HEAD

Submitting patches

Git provides a convinience tool to send generated patches. However, this requires either a properly configured sendmail or a smtp daemon at localhost. You may also use your mail program like Thunderbird instead.

Send patches to abstract-main@lists.sf.net

  git-send-email --to abstract-main@lists.sf.net --subject "..." --compose /var/tmp/out

Another option is to upload the patches to [issue tracker].

Prev