Andy Levy wrote on Thu, May 24, 2012 at 15:33:16 -0400:
> On Thu, May 24, 2012 at 3:20 PM, Marko Asplund <marko.asplund_at_ixonos.com> wrote:
> > On Thu, May 24, 2012 at 10:05 PM, Daniel Shahaf <d.s_at_daniel.shahaf.name>
> > wrote:
> >> ...
> >> Why do you believe you would need to "map" user accounts? What does
> >> "map" mean?
> > Ok, I'll try to explain myself a bit better.
> > I'm migrating a repository from SVN source server A to SVN target server B.
> > SVN server A has account U for user U, while user U's account is named T on
> > server B.
> > SVN server A has accounts that are not present on server B.
> > Target server B is centrally managed and the user management policy prevents
> > creating all the accounts found on source server A.
> > For these reasons I assumed I would need to modify the source repository
> > history so that commits made by user U would be attributed to account T
> > before loading the repository data into server B.
> > Am I making false assumptions here?
> Subversion won't care that the names have changed (there is no
> technical requirement for you to do this at all),
That's correct, but in more words: the value of svn:author revprop is
determined at commit time as the authenticated username, but after the
commit has been done there are _no_ restrictions on the value of the
revprop. It behaves just like every other revision property --- it can
be set to any value.
Agreeing with the remainder of Andy's advice.
(Well, there is a small caveat here --- see svn_repos__validate_prop()
if you want the gory details.)
Received on 2012-05-24 21:51:39 CEST