Home/ Questions/Q 8211827
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-07T10:33:42+00:00

A problem with subversion is that it identifies commits only by the user name.

  • 0

A problem with subversion is that it identifies commits only by the user name. Git for example allows a full name and an email address to be added as meta information to the commit. Some organizations require user accounts that are hard to map to persons. Some of those organizations also require the use of svn. Making this situation workable for code reviewers leads me to the following questions:

  • Is it possible to keep some meta information in the commits so that I can have svn do the mapping?

or if that is impossible,

  • How would I go about doing the mapping on my local system using git-svn?
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You may set custom revision property on any the subversion revision (see http://svnbook.red-bean.com/en/1.7/svn.advanced.props.html for details).

    $ svn propset property_name property_value -r<REV> --revprop
property 'property_name' set on repository revision <REV>

    This could be called in post-commit hook script (the script could have a look at the revision author, look up the short author name to resolve full author information using some mapping file, e.g. authors.txt — see below).

    Git<->SVN tranlation solutions like subgit or git-svn can also use authors.txt mapping in the following format:

    shortname = Long Name <email@example.com>
anothername = Another Long Name <email2@example.com>
...

    Path to authors.txt file should be specified by ‘core.authorsFile’ config option in subgit or ‘–authors-file=’ cli option in git-svn for every git-svn command (for git-svn –authors-file works only for SVN->Git translation, Git->SVN always creates a revision under the username with which; for subgit the option works in both directions).

    • 0