This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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]

Patch submission process


Aloha,
If someone without write privileges submits a patch and gets approval with
a response such as:

>	* example.c (foo): Fix bug.
Ok.

What is the next step?  If the patch is associated with a PR, I just
add a note to the audit trail that points to the approval e-mail.
If the patch isn't associated with a PR, I just create a new one that
points to the patch and approval e-mails so the patch doesn't get lost.
Is there a preferred method for this process?

- glen


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]