owner:esanchez@yaco.es resolution_fixed type_defect | by esanchez@yaco.es
Robert Sparks wrote:
To be more specific:
If I have nominations already in the system for adam@nostrum.com and adam@estacado.net,
after someone uses this merge form to declare adam@nostrum.com primary and adam@estacado.net secondary,
all the nominations already present in the system for adam@estacado.net will need to be associated with
adam@nostrum.com.
Based on what you said above, any nominations that come in for adam@estacado.net will automatically
end up associated with adam@nostrum.com.
Later, when a few nominations for adam@roach.at show up, and the chair goes back to the merge form to
add adam@roach.at to the secondary address list, the existing registration base will have to be rescanned
to find all the already received adam@roach.at nominations to associate them with adam@nostrum.com.
That's what I meant by merge again.
Issue migrated from trac:1034 at 2022-03-04 02:49:41 +0000
owner:esanchez@yaco.esresolution_fixedtype_defect| by esanchez@yaco.esRobert Sparks wrote:
To be more specific:
If I have nominations already in the system for adam@nostrum.com and adam@estacado.net,
after someone uses this merge form to declare adam@nostrum.com primary and adam@estacado.net secondary,
all the nominations already present in the system for adam@estacado.net will need to be associated with
adam@nostrum.com.
Based on what you said above, any nominations that come in for adam@estacado.net will automatically
end up associated with adam@nostrum.com.
Later, when a few nominations for adam@roach.at show up, and the chair goes back to the merge form to
add adam@roach.at to the secondary address list, the existing registration base will have to be rescanned
to find all the already received adam@roach.at nominations to associate them with adam@nostrum.com.
That's what I meant by merge again.
Issue migrated from trac:1034 at 2022-03-04 02:49:41 +0000