On Wed, 2016-02-24 at 16:51 -0800, Junio C Hamano wrote: > Junio C Hamano <gits...@pobox.com> writes: > > > ... > > You can of course standardize on signed int, but because this is a > > collection of flag bits, there is no reason not to choose unsigned. > > > > I _think_ I can fix everything up before pushing out, so please > > check what will appear on 'pu' before rerolling. > > I managed to whip them into shape enough to pass my compilation test > ;-) Other things I had to tweak were small things like whitespace > issues, initializing statics to 0 or NULL, etc.
Got it, thanks. Is there some standard workflow here? I just rebased your version of my series (bd412fa) on top of the prior commit in pu (9db66d9), fixing the few conflicts. (I think there is in general something I'm missing about how to maintain a patch set under the git.git workflow). -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
