On 12/30/2011 09:35 PM, Daniel Shahaf wrote:
Mark Mielke wrote on Fri, Dec 30, 2011 at 20:22:50 -0500:
I think you are not understanding my concern. If svn:author is only
ever displayed to the user - then "authenticated username" may not
be a desirable form to use. For teams of 10 people, sure you can
recognize the uid of everybody in the team. But what about teams of
100, or teams of 1000?
AuthLDAPRemoteUserAttribute cn
Then you can do
% svn commit --username "Daniel Shahaf"
and the logs will show
------------------------------------------------------------------------
r1 | Daniel Shahaf | strftime(...) | 1 line
------------------------------------------------------------------------
We use this for a few services - but note how now instead of losing the
full name, it now loses the unique identifier. In a company of 1,000+
people, there is a good chance for overlap of "cn". There might be only
one Mark Mielke, but other names such as John Sullivan there could be
many. The "cn" is not a unique identifier and cannot be used to key off.
It is for display purposes only.
All of this falls under the banner of thinking small. Small teams. Few
requirements. Most products are like this. Sorry. I know you are just
trying to help. :-)
--
Mark Mielke<m...@mielke.cc>
