Hi everyone, It seems that we're getting more and more contributions from people and we need a better way to manage patches so they don't get dropped on the floor.
The biggest problem is probably that a contributor often doesn't seem to hook up with a specific developer to get a given patch into the tree. Most large open source projects put a substantial burden on the contributor to be persistent and make sure that patches get into the tree, but I wonder if we can come up with some system to streamline things. One starting point is that it's probably time for us to grow up and use the bugtracker a whole lot more than we do. One thought I had was for some way to help users more automatically enter patches into the bug tracking system. In theory, if we put bug numbers into the initial patchbomb message (e.g. the [PATCH 0/7] message), then we could suck all of the resulting patches into the bug database provided that the bug number exists. There's code that does this sort of thing in the mercurial bugzilla extension and it probably wouldn't be too cumbersome to get working with flyspray. The main thing is that I want to come up with a workable idea of how the system should work before I spend any time working on it. Nate _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
