@@ -160,7 +160,7 @@ Then pass an _authors_ option to svn2git pointing to your file:
160
160
161
161
$ svn2git http://svn.example.com/path/to/repo --authors ~/authors.txt
162
162
163
- Alternatively, you can place the authors file into ` ~/.svn2git/authors ` and
163
+ Alternatively, you can place the authors file into ~ /.svn2git/authors and
164
164
svn2git will load it out of there. This allows you to build up one authors
165
165
file for all your projects and have it loaded for each repository that you
166
166
migrate.
@@ -171,10 +171,10 @@ the logs from the svn repository, pulls out all the names from the commits,
171
171
sorts them, and then reduces the list to only unique names. So, in the end
172
172
it outputs a list of usernames of the people that made commits to the svn
173
173
repository which name on its own line. This would allow you to easily
174
- redirect the output of this command sequence to ` ~/.svn2git/authors ` and have
174
+ redirect the output of this command sequence to ~ /.svn2git/authors and have
175
175
a very good starting point for your mapping.
176
176
177
- $ svn log --quiet --xml | grep author | sort -u | sed 's:.*>\(.*\)<.*:\1 = :'
177
+ $ svn -q log http://path/to/root/of/project | grep -E "r[0-9]+ \| .+ \|" | awk '{print $3}' | sort | uniq
178
178
179
179
Debugging
180
180
---------
@@ -183,7 +183,7 @@ If you're having problems with converting your repository and you're not sure wh
183
183
try turning on verbose logging. This will print out more information from the
184
184
underlying git-svn process.
185
185
186
- You can turn on verbose logging with the ` -v ` or ` --verbose ` flags, like so:
186
+ You can turn on verbose logging with the '-v' or ' --verbose' flags, like so:
187
187
188
188
$ svn2git http://svn.yoursite.com/path/to/repo --verbose
189
189
0 commit comments