Update Ch9 section about Mercurial imports to match current hg-fast-export release #1027
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The canonical location for the hg-fast-export tool has been on gihub since 2011.
jnavila
reviewed
Mar 27, 2018
| Hg-fast-export lets us fix this by adding `={new name and email address}` at the end of every line we want to change, and removing the lines for any usernames that we want to leave alone. | ||
| If all the usernames look fine, we won't need this file at all. | ||
| In this example, we want our file to look like this: | ||
| In this example, the same person (Bob) has created changesets under four different names, one of which actually looks correct, and one of which would be completely invalid for a Git commit. Hg-fast-export lets us fix this by turning each line into a rule: `"<input>"="<output>"`, mapping an `<input>` to an `<output>`. Inside the `<input>` and `<output>` strings, all escape sequences understood by the python `string_escape` encoding are supported. If the author mapping file does not contain a matching `<input>`, that author will be sent on to Git unmodified. If all the usernames look fine, we won't need this file at all. In this example, we want our file to look like this: | ||
|
|
There was a problem hiding this comment.
Please maintain the formating of one sentence per line.
There was a problem hiding this comment.
Fixed and revised patch series pushed.
Version 171002 of hg-fast-export changed the format of mapping files to allow arbitrary strings as input and output. Therefore update the example and the description of the format to avoid user confusion (frej/fast-export#116).8000
Users frequently submit summarily rejected patches doing some magit branch and tag name munging to the hg-fast-export project instead of using a mapping file. Try to prevent wasted work by mentioning the existence of mapping files for branches and tags when author mapping files are covered.
jnavila
added a commit
to progit/progit2-fr
that referenced
this pull request
Oct 29, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As maintainer of hg-fast-export I have received at least one issue (frej/fast-export#116) due to the example in Ch9 no longer working with a recent hg-fast-export. In order to avoid future user confusion I propose the changes in this pull request.