> -----Original Message----- > From: [email protected] [mailto:openocd- > [email protected]] On Behalf Of Lennert Buytenhek > Sent: Wednesday, December 16, 2009 2:57 PM > To: Øyvind Harboe > Cc: [email protected] > Subject: Re: [Openocd-development] Codecheck > > On Wed, Dec 16, 2009 at 09:46:29PM +0100, Øyvind Harboe wrote: > > > > for number_of_mallocs: > > > { > > > - fix the file > > > - see if it compiles. > > > - create a patch > > > - send it too you. > > > } > > > > No. > > > > - fix a file(including build it) > > - commit to local git > > While I am of the opinion that git is the greatest thing since sliced > bread, I don't think that it is a good idea to require that people > learn > some VCS they aren't familiar with to contribute to a project. > > E.g. if someone is already familiar with quilt, they can do most of the > local patch management they need without having to learn git (even if > the latter is a good idea, it should not be required upfront). > > In this case, if someone sends a patch series to the list, I don't > think it should matter which VCS was used to manage that patch series > during local development. > _______________________________________________ > Openocd-development mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/openocd-development
If you're already familiar with Quilt, check out StGit. But, really, I haven't found any tool that makes it easier to manage patches than Git. That is, essentially, its purpose. _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
