| foresightyj | |
| Dec 25 2014, 8:49 AM |
| F256471: 2.png | |
| Dec 25 2014, 8:49 AM |
| F256469: 1.png | |
| Dec 25 2014, 8:49 AM |
I had a hard time describing the issue in the title.
I imported a SVN repo to Phabricator (on Dec 22, 2014). If I browse a commit added after the import in Audit, the committed field looks like this:
For commits from the same person before the import, it looks like:
I am not sure if this is a bug or a feature. How do I associate the old commits with the committer so when I raise a concern, the committer will receive an email or a notification?
Update.
My Phabricator was installed in a virtual machine and yesterday the virtual file was corrupted so I had to install Phabricator again.
This time, I added all users first before I imported the SVN repo. I found that all committers were properly associated. So the observation is that when a commit is detected by phabricator, it will try to associate the committer's svn username with a user of the same username in Phabricator . If a particular user was not found at the time of the detected commit, even though the user was added later, Phabricator will not try to resolve old commits.
Thanks, that is our expectation as well. If you add users, you can always reparse commits from the command line tools.
Thanks a lot. For the rest who are interested, I just found that scripts/repository/reparse.php command does this. @epriestley mentioned it in the following stackoverflow thread:
http://stackoverflow.com/questions/21531192/arc-land-applying-with-wrong-user