https://bugzilla.redhat.com/show_bug.cgi?id=1171650

Niels de Vos <nde...@redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|b...@gluster.org            |kaus...@redhat.com



--- Comment #4 from Niels de Vos <nde...@redhat.com> ---
(In reply to Kaushal from comment #3)
> r.g.o now has clickable links to bugzilla.

Great, thanks!

> I'll also add links to Coverity, if I can figure out a direct URI to the CID
> page.

This seems to work:

   
https://scan6.coverity.com:8443/query/defects.htm?projectId=10714&cid=1288824


> About, Change-Id's though, they are supposed to be unique to each review. So
> if a patch were to be backported, it would have a different Change-Id to the
> original.

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

-- 
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=1IbN7wTer9&a=cc_unsubscribe
_______________________________________________
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

Reply via email to