[Lustre-devel] [lustre-devel] merges to b2_<x>

Bruce Korb bruce_korb at xyratex.com
Tue Aug 7 14:00:57 PDT 2012

Hi Andreas,

On 8/7/12 12:45 PM, Andreas Dilger wrote:
>> Another way to do this would be to use the same Change-Id field for the
>> backported patch. One could grep for the Change-Id in the commit logs
>> relatively easily, although I'm not sure how the review system would
>> handle this.
>Using the same Change-Id on two different branches causes heartburn for
>Gerrit, unfortunately.  This has happened by accident a few times, when a
>series of patches were merged into a development branch and then
>accidentally pushed to Gerrit.  It thinks that these previously-landed
>patches are all "in progress" again, and causes every later patch on the
>original branch (usually master) to claim them as open dependencies.

Maybe you could find some script maestro who could auto-insert this
magic tag at the same time the original Change-Id gets inserted?
Commit-Id: anyone?

More information about the lustre-devel mailing list