Jesse Keating wrote:
I was looking for a way to determine the behavior of the master
(for the sake of dist values) without hitting the network, as that would
break git's ability to work offline. The best I could come up with at
the time this code was written was to check and see what other branches
existed, and just increment the biggest one by one. I welcome
suggestions for better ways to manage this.
What was wrong with the good old dist-rawhide target? Making master always
use a rawhide target obviates the need of having to check out what n in
fn-candidate to build for.