×
You must be logged in to change this data. If you don't have an account, please join.
Settings : Aliases
Analyzed
about 1 hour
ago.
based on code collected
about 22 hours
ago.
- Contributions by BP will be attributed to bp Remove Changes will take effect after the next Open Hub report update.
- Contributions by JF will be attributed to jf Remove Changes will take effect after the next Open Hub report update.
- Contributions by TPR will be attributed to ab Remove Changes will take effect after the next Open Hub report update.
- Contributions by JMM will be attributed to djm Remove Changes will take effect after the next Open Hub report update.
- Contributions by AM will be attributed to am Remove Changes will take effect after the next Open Hub report update.
- Contributions by FBS will be attributed to fbs Remove Changes will take effect after the next Open Hub report update.
- Contributions by AB will be attributed to ab Remove Changes will take effect after the next Open Hub report update.
- Contributions by DAS will be attributed to das Remove Changes will take effect after the next Open Hub report update.
- Contributions by BEO will be attributed to beo Remove Changes will take effect after the next Open Hub report update.
- Contributions by Bruni Camillo will be attributed to Camillo Bruni Remove Changes will take effect after the next Open Hub report update.
About Aliases
- If an individual has contributed code to a project under several different committer IDs, you can combine them using aliases.
- An alias will replace one committer ID with another in reports. You specify the ID you wish to replace, and the replacement ID, on the Add Aliases form.
- Aliases do not change your source code history, and Open Hub continues to gather and analyze this history as always. An alias is only an ID mapping for reports and charts.