mikemccand commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1207194931
Yes, sorry for the delay!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
mikemccand commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200960362
Thanks @mocobeta -- can we commit this to the main branch? I can try to add
mappings for the orphan accounts, and then iterate on the still unmapped cases.
--
This is
mikemccand commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200396473
Thanks for the history lesson @uschindler.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
UR
mikemccand commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200396433
OK! Mystery explained then. Apache users (committers+) who had different
Jira id than their Apache id, got renamed in the LDAP migration.
But this left some broke
mikemccand commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200394506
It happens for some other users too:
```
(.venv) beast3:migration[main]$ grep -ri "\[\~" github-import-data/ | wc
331 15583 214620
```
E.g.:
mikemccand commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200393717
Hmm, the thing is, this form `[~thetaphi]` seems to happen quite often:
```
(.venv) beast3:migration[main]$ grep -ri "\[\~thetaphi\]" jira-dump | wc
955
mikemccand commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200309326
This bug happens at least another two times in this converted issue.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log o
