https://bugzilla.redhat.com/show_bug.cgi?id=1428034
--- Comment #6 from Shyamsundar <srang...@redhat.com> --- (In reply to Nigel Babu from comment #5) > Shyam, take a look at this when you get some time -> > https://review.gluster.org/#/c/16901/ (It's a draft and you're CC'd. Need to > be logged in to see) Checked the above and here are some questions: 1) We want the commit message to read "Fixes: #n" OR "Fixes: gluster/glusterfs#n" OR "Updates: #n" OR "Updates: gluster/gusterfs#n". Will the link substitution work for all of the above? 2) When a repo name is not mentioned in the commit message when referencing an issue # (for example: "Updates: #n") the default is gluster/glusterfs is the thought. I understand that later, some other repositories that end up using the same scheme, will have trouble if so, but we want this as the default for the glusterfs repo, so this is a repo specific default, IOW, a commit against repo <name> with no repo reference in the issue #, automatically becomes a link to an issue against that repo <name> 3) Just stating, we will not reference any issue in gluster-specs, we will submit patches to specs that refer to issues in glusterfs repo, like "Updates: gluster/glusterfs#n" 4) I think we should also enforce (if this is the right layer to do it), that either a Fixes/Updates keyword is present before the issue reference. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=yxvG25S8te&a=cc_unsubscribe _______________________________________________ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra