Archives
/
git-filter-repo
mirror of https://github.com/newren/git-filter-repo
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'mg/documentation-typos'

Browse Source 
Signed-off-by: Elijah Newren <newren@gmail.com>
pull/310/head
Elijah Newren 2 years ago
parent bfb86c1b17 7b2840a948
commit 16abc01792
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File

10
Documentation/git-filter-repo.txt
Unescape Escape View File

@ -372,7 +372,7 @@ commits were (or were not) changed.
* All commits in range of the rewrite will be listed, even commits * All commits in range of the rewrite will be listed, even commits
that are unchanged (e.g. because the commit pre-dated when the that are unchanged (e.g. because the commit pre-dated when the
large file(s) were introduced to the repo). large file(s) were introduced to the repo).
* An all-zeros hash, or null SHA, represents a non-existant object. * An all-zeros hash, or null SHA, represents a non-existent object.
When in the "new" column, this means the commit was removed When in the "new" column, this means the commit was removed
entirely. entirely.
@ -384,7 +384,7 @@ references were changed.
* A header is the first line with the text "old", "new" and "ref" * A header is the first line with the text "old", "new" and "ref"
* Reference mappings are in no particular order * Reference mappings are in no particular order
* An all-zeros hash, or null SHA, represents a non-existant object. * An all-zeros hash, or null SHA, represents a non-existent object.
When in the "new" column, this means the ref was removed entirely. When in the "new" column, this means the ref was removed entirely.
[[FRESHCLONE]] [[FRESHCLONE]]
@ -1378,7 +1378,7 @@ Issues specific to filter-repo
Comments on reversibility Comments on reversibility
^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^
Some people are interested in reversibility of of a rewrite; e.g. rewrite Some people are interested in reversibility of a rewrite; e.g. rewrite
history, possibly add some commits, then unrewrite and get the original history, possibly add some commits, then unrewrite and get the original
history back plus a few new "unrewritten" commits. Obviously this is history back plus a few new "unrewritten" commits. Obviously this is
impossible if your rewrite involves throwing away information impossible if your rewrite involves throwing away information
@ -1393,10 +1393,10 @@ likely to be a poor fit for this type of workflow for a few reasons:
* rewriting of commit hashes will probably be reversible, but it is * rewriting of commit hashes will probably be reversible, but it is
possible for rewritten abbreviated hashes to not be unique even if the possible for rewritten abbreviated hashes to not be unique even if the
original abbreviated hashes were. original abbreviated hashes were.
* filter-repo defaults to several forms of unreversible rewriting that * filter-repo defaults to several forms of irreversible rewriting that
you may need to turn off (e.g. the last two bullet points above or you may need to turn off (e.g. the last two bullet points above or
reencoding commit messages into UTF-8); it's possible that additional reencoding commit messages into UTF-8); it's possible that additional
forms of unreversible rewrites will be added in the future. forms of irreversible rewrites will be added in the future.
* I assume that people use filter-repo for one-shot conversions, not * I assume that people use filter-repo for one-shot conversions, not
ongoing data transfers. I explicitly reserve the right to change any ongoing data transfers. I explicitly reserve the right to change any
API in filter-repo based on this presumption (and a comment to this API in filter-repo based on this presumption (and a comment to this

Write Preview
Loading…
Cancel
Save