>> > > Also, dont forget to say its a patch for net-next-2.6 >> > >> > If you're using linux-next, is there a way to tell which tree a >> > patch came from? Obviously in this case it's core networking, but >> > in other cases how does that work? >> >> In this particular case, David will know for sure since patch is very >> recent, but I wanted to make a general advice. >> >> Keep in mind David has to review dozens of patches _per_ day, so netdev >> related patches need some extra cooperation from submitters to help the >> maintainer. >> >> This extra cooperation means to test the patch on either net-next-2.6 or >> net-2.6 tree ;) > > Maybe there is some way to integrate such a suggestion in get_maintainers > or checkpatch? Otherwise, those who work on the code in a more breadth > first way don't have much chance of knowing or remembering this advice. > > julia I think Julia's observation is really on the nail, I wish there were some way of doing this? If new or random testers or reviewers out there aren't tracking/following a particular tree/project already - i.e. if they don't _know_ beforehand, aren't they going to just assume using linux-next is correct (at least that's what I do)? Knowing what branch to most productively test patches against beforehand might encourage more testers and submissions and also could make maintainer's jobs a bit easier. Cheers Julie -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
