use assert(0) instead of exit(1)

When a fatal error (unaligned memory etc.) is detected, gf-complete should
assert(3) instead of exit(3) to give a chance to the calling program to
catch the exception and display a stack trace. Although it is possible
for gdb to display the stack trace and break on exit, libraries are not
usually expected to terminate the calling program in this way.

Signed-off-by: Loic Dachary <loic@dachary.org>
(cherry picked from commit 29427efac2ce362fce8e4f5f5f1030feba942b73)
gitignore: add src/.dirstamp

Signed-off-by: Greg Farnum <gfarnum@redhat.com>
Revert "Removed PDF from the repo and added a note in the README that describes how to"

This reverts commit 9311b4fc107da2f2e9a2624520cfe2ffd216af53.
documentation: update with jerasure.org new home

Signed-off-by: Loic Dachary <loic@dachary.org>
Merge branch 'wip-documentation' into 'master'

documentation

updates to replace URLs that do not contain useful information

See merge request !3
Merge branch 'wip-exit-v2' into 'master'

exit v2

See merge request !2
Merge branch 'wip-dirstamp-ignore' into 'master'

dirstamp ignore

See merge request !1