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! On Sat, 24 May 2014 02:43:38 +0530, Siddhesh Poyarekar <siddhesh@redhat.com> wrote: > patchwork.sourceware.org > close patches you know you have already pushed into master. Does that mean changing the state to ÂAccepted (or ÂCommittedÂ, once that has been added), or ticking the ÂArchived box, or both? What's the meaning of the ÂArchived box? > Please also take time to review the workflow for patch reviews: > > https://sourceware.org/glibc/wiki/Patch%20Review%20Workflow So, does patchwork's ÂDelegate to Patch Property equal Bugzilla's ÂAssigned To field? And, it is not totally clear to my why the Patch Review Workflow suggests to Ânot change the status of the patch if Âchanging the Delegate to value to their patchwork usernameÂ? "In a perfect world", after a patch review, during which ÂDelegate to has been set to the reviewer(s), should it then be changed to the person who is responsible for committing the patch (which may be the submitter, or the reviewer, or someone else), together with changing the state to ÂAcceptedÂ? GrÃÃe, Thomas
Attachment:
pgpCBI9n2SC2y.pgp
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |