[llvm-dev] [cfe-dev] Bugzilla migration is stopped again
Geoffrey Martin-Noble via llvm-dev
llvm-dev at lists.llvm.org
Wed Dec 8 15:54:32 PST 2021
A couple of potentially relevant pieces of information. At least under the
default notification settings, neither adding a label, nor editing a
comment sends a notification. So it should be possible to fix things that
require doing either of these things after the fact. (e.g. Arthur's
suggestion could be implemented *after* the issue is in GitHub, when the
URL is known)
On Wed, Dec 8, 2021 at 2:51 PM Anton Korobeynikov via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> > Two more things I've noticed while spot-checking:
> > https://github.com/llvm/llvm-bugzilla-archive/issues/36617
> > - Bugzilla lets you attach file attachments; GitHub doesn't. Attachments
> are not preserved by the migration.
> You are wrong again. Attachments are preserved:
>
> https://github.com/llvm/llvm-bugzilla-archive/issues/36617#issuecomment-980994333
> Will you please next time check your claims more carefully?
>
> > - Bugzilla comments are numbered, so people sometimes say e.g. "see
> comment 16"; GitHub comments are not numbered. The migration script might
> consider automagically turning these references into hyperlinks similar to
> how Bugzilla does it.
> It cannot. The URL is not known before the issue is on GitHub as the
> URL is assigned by GitHub.
>
> --
> With best regards, Anton Korobeynikov
> Department of Statistical Modelling, Saint Petersburg State University
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20211208/a0cfdad8/attachment.html>
More information about the llvm-dev
mailing list