On Monday 2011-03-21 23:43, Patrick McHardy wrote: >> >> I find deletions just for the sake of making a release not very >> aesthetic to the git history. It duplicates commits in a way, but >> above all, interrupts the flow when tracking changes with "git >> blame". Better branch off earlier... >> ~/envisioning a git topic for the next NFWS.~ > >> So yeah, time for a release or so. Not for 2.6.38, but for the >> general benefit. > >Yeah, that's my opinion as well. Which means branching and >removing new extensions from that branch. The removal can be avoided if it is branched from the right point. Right, this was not exactly done like that in the last cycle, which is why I can see why you would like to hold a release. >That's really not the question, I'm not going to release >extensions for kernel modules which are so far in -rc. Makes sense. So then in that case, let's hold. Most distros had just fixated their version anyway, so throwing something out the door now does not yield that much. Regarding the history tree, let's start doing it with better branching from now. I offer to take up all the patches (since that's just minimally more than already doing), and place them into the right spot in the tree such that there be no deletions or cherry-picks required in future. -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
