To make sure that we are talking about the same thing, here is indeed a bug report originally written by me in launchpad but attributed to some Fabien in this new database: https://gitlab.com/orsonmmz/kicad-bug-tracker/issues/7600 (screenshot attached in case you see it differently).
su 10. marrask. 2019 klo 18.52 Eeli Kaikkonen ([email protected]) kirjoitti: > I got a false impression that importing the bug database currently has > some problem because those reports which I opened seemed to be written > originally by some mysterious username, while the subsequent comments were > correctly attributed. This led to me asking about it here. These kinds of > false impressions of bugs in the importing process could be avoided if it > was re-imported from scratch to create correct data (supposing that it was > a bug which orson fixed and now works correctly). > > Eeli Kaikkonen > > su 10. marrask. 2019 klo 18.43 Seth Hillbrand ([email protected]) > kirjoitti: > >> On 2019-11-10 08:33, Eeli Kaikkonen wrote: >> >> OK. Would it be worth re-importing everything even for this test database >> to avoid false impressions? >> >> Eeli Kaikkonen >> >> >> What false impression? Is there a report that is listed as being created >> by different people in launchpad vs. GitLab? >> >> >> KiCad Services Corporation [image: KiCad Services Corporation Logo] >> Seth Hillbrand >> *Lead Developer* >> +1-530-302-5483 <+12126039372> >> Davis, CA >> www.kipro-pcb.com [email protected] >> https://twitter.com/KiProEDA <https://twitter.com/KiProEDA> >> https://www.linkedin.com/company/kicad >> <https://www.linkedin.com/company/kicad> >> >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
