[Insight-developers] Migration guides docs editing

[Julien Jomier]

This is currently not possible because there is a one-to-one mapping 
between entries in the migration guide and gerrit-changeId. It seems 
that if you are doing additional changes it should be the same 
gerrit-changeid but with a new patch applied to that branch.

Julien

On 16/08/2011 18:29, Cory Quammen wrote:
> On Tue, Aug 16, 2011 at 12:16 PM, Julien Jomier
> <julien.jomier at kitware.com>  wrote:
>>> It's definitely the right thing to do. Make it easy for the users of
>>> the migration guide, including referencing multiple gerrit change IDs.
>>> If we have to, we should adapt our processing of the xml documents to
>>> account for this fact.
>>
>> I think Cory is saying that the previous changes are obsolete, is that
>> correct? If that's the case then the gerrit change ID should be the same.
>
> The original changes are not obsolete; I've made additional changes,
> though, which makes the existing migration guide obsolete (or at least
> incomplete).
>
> Can I add a second<Gerrit-ChangeId>  element, e.g.
>
> <Gerrit-ChangeId>
> Ic4f6c1733ae75173079af4e684a34827dadbd99c
> </Gerrit-ChangeId>
>
> <Gerrit-ChangeId>
> I1588e79c400f9035dde85f491cfaf3965063f953
> </Gerrit-ChangeId>
>
> ?
>
> Thanks,
> Cory
>
>