Hi,

At some point in the past, some lead developer wrote that tickets that
were created w/ an attached patch may contain the [PATCH] keyword in
the summary, while existent tickets that were attached a patch after
their creation should not be renamed.

IMHO this rule should be kept, as it makes ticket history easier to
follow w/ email clients for instance.

I renamed two tickets like you described above. I didn't know about this policy, so I'm sorry if this wasn't adequate. How do you mark a ticket as having a patch for review?

-- Remy

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to