search for: movefrom

...is messed up, the repo can be deleted, and the process run again, until we get a result we like. 2. The numbering can be fully-controlled. Once the bugs are migrated to *some* github repository, individual issues can then be "moved" between repositories, and github will redirect from the movefrom-repository's bug to the target repository's bug. We could also just have llvm.org/PR### be the url only for legacy bugzilla issue numbers -- and have it use a file listing the mappings of bugzilla id -> github id to generate the redirects. (GCC just did this recently for svn revision nu...

...), buffer, type="class", trace=FALSE) > names(solution) [1] "alpha" "alpha0" "lambda" "alpha00" "Error" "SumEps" [7] "Size.Elbow" "Elbow" "Moveto" "Movefrom" "Obs.step" "Step" [13] "kernel" "param.kernel" "x" "y" "call" > solution$alpha0 [1] 130.785000 108.685000 106.210000 86.130000 85.485000 71.176837 68.197549 67.660686 [9] 60.84789...

...an be deleted, and the process > run again, until we get a result we like. > 2. The numbering can be fully-controlled. > Once the bugs are migrated to *some* github repository, individual issues > can then be "moved" between repositories, and github will redirect from the > movefrom-repository's bug to the target repository's bug. > > We could also just have llvm.org/PR### <http://llvm.org/PR#%23%23> be the > url only for legacy bugzilla issue numbers -- and have it use a file > listing the mappings of bugzilla id -> github id to generate the redir...

...ed, and the process run again, until we get a result we like. >>> 2. The numbering can be fully-controlled. >>> Once the bugs are migrated to /some/ github repository, individual issues can then be "moved" between repositories, and github will redirect from the movefrom-repository's bug to the target repository's bug. >>> >>> We could also just have llvm.org/PR### <http://llvm.org/PR#%23%23> be the url only for legacy bugzilla issue numbers -- and have it use a file listing the mappings of bugzilla id -> github id to generat...

...; process run again, until we get a result we like. > >> 2. The numbering can be fully-controlled. > >> Once the bugs are migrated to /some/ github repository, individual > issues can then be "moved" between repositories, and github will redirect > from the movefrom-repository's bug to the target repository's bug. > >> > >> We could also just have llvm.org/PR### <http://llvm.org/PR#%23%23> > <http://llvm.org/PR#%23%23> be the url only for legacy bugzilla issue > numbers -- and have it use a file listing the mappi...

...e process run again, until we get a result we like. > >>> 2. The numbering can be fully-controlled. > >>> Once the bugs are migrated to /some/ github repository, individual issues can then be "moved" between repositories, and github will redirect from the movefrom-repository's bug to the target repository's bug. > >>> > >>> We could also just have llvm.org/PR### <http://llvm.org/PR#%23%23> <http://llvm.org/PR#%23%23 <http://llvm.org/PR#%23%23>> be the url only for legacy bugzilla issue numbers -- and hav...

Hi, I wanted to continue discussing the plan to migrate from Bugzilla to Github. It was suggested that I start a new thread and give a summary of the proposal and what has changed since it was originally proposed in October. == Here is the original proposal: http://lists.llvm.org/pipermail/llvm-dev/2019-October/136162.html == What has changed: * You will be able to subscribe to notifications