Commit f63b3141 authored by thomas.forbriger's avatar thomas.forbriger
Browse files

master [TASK][DOC]: describe line of branch ancestry

parent 995ffadc
......@@ -19,7 +19,7 @@ EDITBASH=$(patsubst ./%,%,$(shell find . -name \*.sh))
EDITAWK=$(patsubst ./%,%,$(shell find . -name \*.awk))
EDITMAKE=$(patsubst ./%,%,$(shell find . -name Makefile)) \
$(filter-out %.bak,$(patsubst ./%,%,$(shell find . -name makefile\*)))
EDITREADME=$(patsubst ./%,%,$(shell find . -iname REA\*ME))
EDITREADME=$(patsubst ./%,%,$(shell find . -iname REA\*ME -o -name \*.md))
......@@ -16,16 +16,27 @@ Just run
make all
Further details for compilation and installation are given in
See [software/README](software/README) for current status if maintained
See [software/README](software/README) for current status of maintained
See [CHANGELOG](CHANGELOG) for recent modifications (bug fixes, new features,
Source code is provided on branch `vendor`.
In order to make software history transparent and to support future vendor
updates, the source code is organized in a hierarchy of repository branches.
The order of ancestry is `vendor` -> `unix` -> `master`, where `vendor` refers
to the most recent import from the
[vendor repository](
The most recent additions for Linux users are available on branch `master`.
A second line of ancestry, where branch names end on `-with-examples`,
provides the same contents but with toy examples and example data added.
### branches
#### published branches
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment