On Monday 23 June 2008 12:23:45 Acinonyx wrote: > > From my perspective, using the ticket system would be best. Then I could > > submit my patch and forget about it afterwards, because I would be > > notified by mail when someone made changes to the ticket. > > This surely helps the developers keep track of the submitted patches but I > think it makes it more time consuming to apply them than emailed patches.
Why? I would assume that saving the patch from either a mail client or a web page prior to applying it would consume the same amount of time. Unless of course, your mail agent has some sort of shortcut for applying patches. For me, sending in patches in the required mail format was somewhat painful, because I first had to get familiar with it. Additionally, the default configuration of my mail agent (KMail) isn't suitable, so I first had to change the settings. What's even worse, it doesn't remember when I turn off word-wrap, so I have to turn it off manually for each message I send. It's not really straight-forward if you don't submit patches on a regular basis. I tend to forget things like that. On a web page, you're guided to do the right thing automatically. I'm not too delighted considering that it took me almost as long to get the patch submitted as it took me to make it ... On the other hand, all this would be bearable, if we just made sure unhandled patches would be brought to the devs' attention in one way or the other. I don't really see how this could be achieved other than the two suggestions by RB. _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
