[Babel-users] [PATCH] babel: Basic support for a version string

[Dave Taht]

d at nuc-client:~/git/babeld$ ./babeld -v
babeld-1.5.1-65-g8950d3b IPV6_SUBTREES built 02:51:33 Apr  5 2015

I must have 11 different versions of babel deployed on my network
by now, and it is going to be a hassle to track them all down to fully
deploy the source specific stuff next month.

1) It is not clear to me how to generate a release tarball with the
VERSION file,
instead of git.

I bummed the tiny script from the dnsmasq tree to parse the release
tags and supply the git commit it was based on. Hopefully simon has
madness and method somewhere. bugging him.

(why is it I am always working on dnsmasq AND babel at the same time?)

(no, simon, I have not get any more dnssec testing done yet. Tomorrow (today))

2) I thought about adding the version to the info supplied to
babelweb, but did not poke there

3) It is not clear from reading the man page if diversity routing and
rtt based stuff
can be enabled at the same time. If both are set, who wins?

4) Also, diversity routing is the default for me, and I would suspect
the default for others, so I would suggest flipping the default to
true in 1.6.

I am not big on inline patches (from gmail), so it is attached and
also available here.

http://snapon.lab.bufferbloat.net/~d/0001-Add-support-for-a-version-string.patch

Should I use github pull requests instead?
-- 
Dave Täht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Add-support-for-a-version-string.patch
Type: text/x-patch
Size: 3810 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/babel-users/attachments/20150405/2daba277/attachment.bin>