Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: >> Yup. I think they are now in good shape to be among the first to >> graduate post release. Building the warning facility necessary to >> start dropping the $GIT_DIR/branches/ support would be too late for >> this cycle, but now this topic is independent from that, so it may >> even be worth considering to have it in the upcoming release. > > I see that you made up your mind and graduated the branch to `master` > already. Very happy about that, and of course I hope that this was > intentional ;-) Yup. Thanks, as usual, for all the help. I didn't see anything remotely problematic in the latest round of the series (except for possibly the "resurrect '#if 0'ed out block of code in git.c" piece but that one is a simple enough change in a reasonably dormant codepath that is easy to revert if/when unforeseen issues are found by people with different/unanticipated use patterns).
