Nemcio/git-remote-hg
1
0
Fork 0
mirror of https://github.com/mnauw/git-remote-hg.git synced 2025-10-28 07:06:09 +01:00
Code Issues Packages Projects Releases Activity

README: clarify documentation on strip recovery

Browse Source
This commit is contained in:
Mark Nauwelaerts
2016-10-18 21:31:57 +02:00
parent af96a84c98
commit e759d5232d
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.asciidoc
View File

@@ -195,8 +195,8 @@ To tweak how 'git-remote-hg' decides on a copy/rename, use e.g:
Other than <<no-limitations, removing the limitations>> as mentioned above, Other than <<no-limitations, removing the limitations>> as mentioned above,
a number of issues (either so reported in a number of issues (either so reported in
https://github.com/felipec/git-remote-hg/issues[issue tracking] or not) have been https://github.com/felipec/git-remote-hg/issues[issue tracking] or not) have been
addressed here, e.g. notes handling, `fetch --prune` support, recovering addressed here, e.g. notes handling, `fetch --prune` support, correctly fetching
from a `strip` on remote repo, tracking remote changes to import (if any) in a after a `strip` on remote repo, tracking remote changes to import (if any) in a
safe, robust and efficient way, etc. Some of these have been highlighted above. safe, robust and efficient way, etc. Some of these have been highlighted above.
For example, the `refs/hg/...` refs are really an implementation detail For example, the `refs/hg/...` refs are really an implementation detail