Would a crazy option 4 be to add VENDOR_APLOGNO() which could add a prefix
to the log number to be used in any patches?
For example, V_APLOGNO('R', 123) could produce AHR123
This would make it clear that the error comes from a patch from another
distribution.
- Y
Sent from a device with a very small keyboard and hyperactive autocorrect.
On Tue, Dec 1, 2020, 9:33 AM Joe Orton <[email protected]> wrote:
> Very occasionally we backport patches to RHEL's httpd package in a way
> that introduces new or different logging output from 2.4/trunk. I'm
> wondering if there is any opinion about vendors asking for for a small
> (say, 100?) reserved range of APLOGNO() space to use for such cases?
> Basically I'd just commit "next-number += 100" and use that range within
> downstream patches since they are then reserved upstream.
>
> 1) No, we should discourage vendors from such divergence.
>
> 2) Yes, they are just numbers, I don't care.
>
> 3) Yes, but commit to maintaining a public URL with documentation for
> each log message used or something similar.
>
> Thoughts?
>
> Regards, Joe
>
>
