-
Andy Webber authored
At present, DW shows the username on the bottom left under "logged in as", and the login name for "last modified", "locked by" and under revisions/recent changes. In a corporate environment, particularly when integrated with a Single Sign-On system, the login name may be somewhat unfriendly. This patch makes the "logged in as" the same as the value used elsewhere and also allows an admin to decide whether it should be the login name, username or e-mail address that is displayed. The e-mail address may also, optionally, be a mailto: link. E-mail addresses are obfuscated according to the 'mailguard' setting. The default behaviour is to show the login name which is no change from previous behaviour for the "last modified"/"locked by"/revisions/"recent changes", but is a change for the "logged in as". darcs-hash:20081001152914-6ad63-9cd7174068ac55de381f1318a4401f8c51de5b0c.gz
Andy Webber authoredAt present, DW shows the username on the bottom left under "logged in as", and the login name for "last modified", "locked by" and under revisions/recent changes. In a corporate environment, particularly when integrated with a Single Sign-On system, the login name may be somewhat unfriendly. This patch makes the "logged in as" the same as the value used elsewhere and also allows an admin to decide whether it should be the login name, username or e-mail address that is displayed. The e-mail address may also, optionally, be a mailto: link. E-mail addresses are obfuscated according to the 'mailguard' setting. The default behaviour is to show the login name which is no change from previous behaviour for the "last modified"/"locked by"/revisions/"recent changes", but is a change for the "logged in as". darcs-hash:20081001152914-6ad63-9cd7174068ac55de381f1318a4401f8c51de5b0c.gz
Code owners
Assign users and groups as approvers for specific file changes. Learn more.