[Audacity-quality] request for patch naming convention
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Vaughan J. <va...@au...> - 2013-12-18 23:15:41
|
I'm doing a quick sweep of patch_ready Bugzilla entries. It would help a lot if there were a convention to the patch names. I don't seen any consistency in them now. Some refer to the bug title, some to what's fixed, etc. Specifically, I'd like to have "bugN" as the prefix. Whether there's more, is up to the patch submitter. For example, instead of "macwidth.patch" for bug 646, make it "bug646.patch" or "bug646_macwidth.patch". (Not picking on you, LLL -- this was just the nth one that made me think there should be a better way to track them in my d/l folder.) This will also help in distinguishing patches that don't have a Bugzilla entry -- they won't have the prefix. Or could be prefixed with "enh", e.g. If we agree on this, it can be documented in the 'how to submit patches' wiki page. Thanks, Vaughan |