Re: v2.1.x branch renamed to v2.x.x

On 10/28/2012 10:12 AM, Arran Cudbard-Bell wrote:

Someone was complaining about the branch name v2.1.x being confusing now were on 2.2.0. There's no point in maintaining a branch for v2.1.x because there's never going to be further development.

To fixup branches in your fork:

Eww.. Related: has something funny happened to the "master" branch: From git://github.com/FreeRADIUS/freeradius-server + 15433ac...d7b1d55 master -> upstream/master (forced update) ...and when I merge "upstream/master" into "master" I didn't get a fast-forward merge, which I should because I keep my "master" pristine, and only ever branch it.