On Wed, Nov 20, 2019 at 8:33 PM Kyotaro Horiguchi
<horikyota.ntt@gmail.com> wrote:
> So, still any ongoing patch can stamp on another when it is committed
> by certain probability (even if it's rather low)). And consecutive
> high-OID "hole"s are going to be shortened and decrease throgh a year.
Right.
> By the way even if we work this way, developers tend to pick up low
> range OIDs since it is printed at the beginning of the output. I think
> we should hide the whole list of unused oids defaultly and just
> suggest random one.
It is still within the discretion of committers to use the
non-reserved/development OID ranges directly. For example, a committer
may prefer to use an OID that is close to the OIDs already used for a
set of related objects, if the related objects are already in a stable
release. (I'm not sure that it's really worth doing that, but that's
what the policy is.)
--
Peter Geoghegan