https://bugzilla.redhat.com/show_bug.cgi?id=1557127
Bug ID: 1557127
Summary: github issue update on spec commits
Product: GlusterFS
Version: mainline
Component: project-infrastructure
Assignee: b...@gluster.org
Reporter: pkara...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
Description of problem:
I think most of the developers are used to seeing an update on the issue when a
patch is sent on it, referring to it. At the moment for spec patches, the
behaviour seems to be that we get the update after the commit is merged. Could
we change this to be similar to what happens on FS? i.e. we get an update on
the github issue as soon as a patch is sent.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
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=Zp4quktqvb&a=cc_unsubscribe
_______________________________________________
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra
