> OK, I understand that but when downloading the latest > version you're writing about and compiling it, it says "20121228"
I see what you mean. Those date variables are updated only when Willy releases a new -dev release; which is a manual process as you can see from git commit [1]. In fact, in git you still see the date 20121228, for example in the file VERDATE [2] (or 1.5-dev17 in VERSION). A snapshot is just a clone of the current git tree, and therefore, doesn't contain any updated dates. Of course it does contain the bugfixes though. In our case, when checking the commit Willy talked about earlier today [3] and comparing the actual source in the snapshot tarball, you will see that the bugfix is already in there. I understand this can be confusing if you see something like this on your shell: > lukas@dev:~/src/haproxy-ss-20121230$ ./haproxy -v > HA-Proxy version 1.5-dev17 2012/12/28 > Copyright 2000-2012 Willy Tarreau <[email protected]> In this case, the binary says "1.5-dev17 2012/12/28", while it actually is "ss-20121230". Long story short, if you are compiling the ss-20121230 tarball you are really using the latest source code including all fixes. That means the issue you see was not caused by the bug Willy mentioned, but by something else. [1] http://haproxy.1wt.eu/git?p=haproxy.git;a=commitdiff;h=a3ecbd902345862b4a399f8a0bbaace6bc7ba4e6 [2] http://haproxy.1wt.eu/git?p=haproxy.git;a=blob_plain;f=VERDATE [3] http://haproxy.1wt.eu/git?p=haproxy.git;a=commitdiff;h=c5c61fcf453adf396a21308be373f499b7953a05
