This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi, In an attempt to make progress on the subject of choosing a tool to track patches in glibc, I had created a patchwork instance on my server[1] for people to try their hand at it and to see what kind of changes we need to the tool to suit our requirements. A few of us signed up and tried their hand at using patchwork and so far there haven't been any complaints. Following Carlos' suggestion, I created a wiki document to define a workflow around patchwork[2], which got some feedback and subsequent editing. Since there haven't been any further questions or comments on either the choice of tool or the workflow, I propose that we create the final instance on sourceware and start using it. Does anyone have any objections to it? I volunteer to help with setup and migration, but I don't have access to the sourceware server beyond the glibc git repo, so I'd appreciate help on that end. The setup and migration sequence: - Set up the patchwork application and database on sourceware and configure it to use SSL by default. - Migrate earlier patches and state from patchwork.siddhesh.in - Subscribe a user for patchwork to libc-alpha - Have all maintainers sign up Siddhesh [1] http://patchwork.siddhesh.in [2] https://sourceware.org/glibc/wiki/Patch%20Review%20Workflow
Attachment:
pgpsYDeMdegHL.pgp
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |