llvm dev - Dec 2021 - Bugzilla migration is stopped again

On Sat, Dec 4, 2021 at 1:19 AM Anton Korobeynikov via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Dear All,
>
> I hate to say this, but the migration was stopped again. Now it seems
> that GitHub does not rewrite issue references properly during the
> transfer (sick!). Let me show what the problem is exactly:
>
> Consider two issues: A and B, where A will reference B and B will
> reference A. In our case this is used to model various relations like
> "duplicates / is duplicated by", "blocks / is blocked
by", "depends on
> / required by". So, in bz archive A will reference B as #B and B
> will reference #A.
>
> Now, let's migrate A. The references will be rewritten. #B =>
> bz-archive#B and #A => llvm-project#A. However, after migration of B
> only one reference is rewritten llvm-project#A => #A, the bz-archive#B
> link in the issue A will not be rewritten and therefore a dangling
> reference will appear.

To clarify, will those bz-archive#B references just not look as nice, or do
they not work at all? It was my understanding that bz-archive#B will
redirect to llvm-project#B2, in which case this doesn't seem overly
problematic.

Regards,
Nikita
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20211204/98944b80/attachment.html>

> To clarify, will those bz-archive#B references just not look as nice, or do
they not work at all? It was my understanding that bz-archive#B will redirect to
llvm-project#B2, in which case this doesn't seem overly problematic.
They will be just text. No redirect.

-- 
With best regards, Anton Korobeynikov
Department of Statistical Modelling, Saint Petersburg State University