https://bugzilla.redhat.com/show_bug.cgi?id=1171650
--- Comment #5 from Kaushal <kaus...@redhat.com> --- (In reply to Niels de Vos from comment #4) > This seems to work: > > > https://scan6.coverity.com:8443/query/defects.htm?projectId=10714&cid=1288824 > It keeps redirecting me to my coverity user dashboard. > > Backports often should have the same Change-Id. This makes it easy to > identify backports and their original change. A Change-Id needs to be unique > per branch, different branches (master, release-3.7, ...) can have the same > Change-Id. Example: > > http://review.gluster.org/#/q/I62168a0ab4f0c78e61987371ae75a0d2dd56ced8 The gerrit documentation recommends having different change-ids for backports. Each backport is a unique commit, so it should have a unique change-id for gerrit to be able to track it. This was how I thought gerrit should have worked, but apparently you can have duplicate change-ids. Whenever I've backported changes I've always had the change-id regenerated. I believe this is how most of the developers did backports. I'll add the commentlink setting anyway. -- 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=GLoSpbvCLo&a=cc_unsubscribe _______________________________________________ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra