On Wed, Oct 27, 2010 at 5:34 PM, Daniel Pittman <[email protected]> wrote: > I am going to mention patchwork again - a bunch of Linux kernel projects use > it to monitor patches that go past on their lists; it could easily capture, in > fact, not just the deliberate dev list things, but also the user list set of > patches. > > http://ozlabs.org/~jk/projects/patchwork/ > > You can see it in anger here: https://patchwork.kernel.org/
Daniel or anyone else that can help with patchwork, Thanks for suggesting this tool, it seems very useful in concept. Do you or someone else know where to find a usable version of the source code -- like the version or fork running the Linux kernel patch site you linked to? I spent some time reviewing patchwork with our sysadmin, and it was a mess. The code and instructions were filled with errors, it expected us to somehow guess how to set it up by entering values into undocumented, ambiguously-named database fields, and despite fixing and working around many problems to actually get it running, we gave up when we couldn't figure out how to fix the exceptions being thrown by the authentication and user management system. There were no branches, no tags, and even checking out older versions didn't get us a usable version. Thoughts? -igal -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
