Re: New Patchwork beta
On Aug 21, 2008, at 5:52 PM, Josh Boyer wrote: On Thu, 2008-08-21 at 15:32 -0500, Kumar Gala wrote: Some feedback: * Can we increase the font size a bit? NOO. Just use CTRL-SHIFT-+. ok * For the list of patches can we change the background of every other line (light gray) That would work well. thanks this looks better, easier to read. * Parsing subject header for determining state -- [RFC] That is going to fail miserably because people tend to do silly things like post final patches in the middle of an [RFC] thread. gotcha. Now that I can log in, can I get maintainer privileges (user: galak) also is it possible to put the patch controls in a separate frame so they are always visible (dont have to scoll to the bottom to find them). - k ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [Cbe-oss-dev] New Patchwork beta
Hi Kumar, [trimming CC list] Now that I can log in, can I get maintainer privileges (user: galak) Yep, you should already have maintainer privs for linuxppc-dev also is it possible to put the patch controls in a separate frame so they are always visible (dont have to scoll to the bottom to find them). I'm trying to avoid using frames; it makes it hard to link to individual pages, and makes patch updating much more complex. However, there shouldn't be a need for too much scrolling now - to prevent patch lists from growing too long, the results are paginated into groups of 100 patches. Also, when there are more than about 30 patches on a page, you'll get a small link on the left-hand side to scroll straight to the form area. Is this OK? Cheers, Jeremy ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [Cbe-oss-dev] New Patchwork beta
On Aug 22, 2008, at 3:55 AM, Jeremy Kerr wrote: Hi Kumar, [trimming CC list] Now that I can log in, can I get maintainer privileges (user: galak) Yep, you should already have maintainer privs for linuxppc-dev also is it possible to put the patch controls in a separate frame so they are always visible (dont have to scoll to the bottom to find them). I'm trying to avoid using frames; it makes it hard to link to individual pages, and makes patch updating much more complex. However, there shouldn't be a need for too much scrolling now - to prevent patch lists from growing too long, the results are paginated into groups of 100 patches. Also, when there are more than about 30 patches on a page, you'll get a small link on the left-hand side to scroll straight to the form area. Is this OK? probably, will need to see when we get more patches how this actually looks. I know it was a big annoyance w/v1. - k ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
New Patchwork beta
Hi all, I've just put up a new beta of patchwork: http://patchwork2.ozlabs.org/ I intend to replace the existing patchwork with the new code, but would like to get it tested first. There aren't many patches in the system at the moment, but it'll receive patches from the relevant lists. I'll also import a set of existing mails tomorrow, to give some sample data to test with. One important note - after beta testing, I'm planning to clear the test database and start from scratch. So, don't go spending too much time updating patches! However, have a play with the new site, let me know what breaks, and any suggestions for changing, and we can work towards a full replacement for the current site. Some differences from the old patchwork: * Patches can now be 'delegated' to other maintainers - this means that maintainers can offload subsystem-specific patches to other maintainers. * Anyone can create an account, and work with bundles, and manage their own patches. * Pagination. No more 10MB patch lists! * Bundles can be made public, allow users to share patchsets * Better filtering interface Project Maintainers: Create an account, then send me your username, and I'll add maintainer privileges to your account. Again, don't go too crazy with the maintaining work, as it'll all be cleared out once we replace patchwork.ozlabs.org Also: bazaar-ng, linux-mtd and linux-embedded folks: are you still using patchwork? Existing patches: After talking to the powerpc maintainers, we've decided that we're going to start with a clean slate, and not import patches from the existing patchwork database. If you'd prefer to keep current patches for your project, let me know. This will be a bit of work, but I'm sure we can work something out. Happy patchworking, Jeremy ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: New Patchwork beta
Some feedback: * Can we increase the font size a bit? * For the list of patches can we change the background of every other line (light gray) * Parsing subject header for determining state -- [RFC] w/o being able to log in that's my initial two cents. Both otherwise it looks good and seem much faster than the old version. - k ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: New Patchwork beta
On Thu, 2008-08-21 at 15:32 -0500, Kumar Gala wrote: Some feedback: * Can we increase the font size a bit? NOO. Just use CTRL-SHIFT-+. * For the list of patches can we change the background of every other line (light gray) That would work well. * Parsing subject header for determining state -- [RFC] That is going to fail miserably because people tend to do silly things like post final patches in the middle of an [RFC] thread. josh ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
