git-reset.txt: clarify documentation
PATCH 1/1 git-reset.txt: clarify documentation
git-reset.txt contained a missing "a" and "wrt". Fix the missing "a" for correctness and replace "wrt" with "with respect to" so that the documentation is not so cryptic.
--- Documentation/git-reset.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
Documentation/git-reset.txt +5 -5
@@ -428,11 +428,11 @@ working index HEAD target working index HEAD `reset --merge` is meant to be used when resetting out of a conflicted merge. Any mergy operation guarantees that the working tree file that is -involved in the merge does not have local change wrt the index before -it starts, and that it writes the result out to the working tree. So if -we see some difference between the index and the target and also -between the index and the working tree, then it means that we are not -resetting out from a state that a mergy operation left after failing +involved in the merge does not have a local change with respect to the +index before it starts, and that it writes the result out to the working +tree. So if we see some difference between the index and the target and +also between the index and the working tree, then it means that we are +not resetting out from a state that a mergy operation left after failing with a conflict. That is why we disallow `--merge` option in this case. `reset --keep` is meant to be used when removing some of the last
Signature · 1 line
2.21.0.260.g8f7229c82f
Quoted 3 lines · Denton Liu
git-reset.txt contained a missing "a" and "wrt". Fix the missing "a" for correctness and replace "wrt" with "with respect to" so that the documentation is not so cryptic.
Could you try again without unrelated reflowing of the text?
Thanks.
Quoted 27 lines
Signed-off-by Denton Liu <[email protected]>--- Documentation/git-reset.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)Documentation/git-reset.txt +5
-5@@ -428,11 +428,11 @@ working index HEAD target working index HEAD `reset --merge` is meant to be used when resetting out of a conflicted merge. Any mergy operation guarantees that the working tree file that is -involved in the merge does not have local change wrt the index before -it starts, and that it writes the result out to the working tree. So if -we see some difference between the index and the target and also -between the index and the working tree, then it means that we are not -resetting out from a state that a mergy operation left after failing +involved in the merge does not have a local change with respect to the +index before it starts, and that it writes the result out to the working +tree. So if we see some difference between the index and the target and +also between the index and the working tree, then it means that we are +not resetting out from a state that a mergy operation left after failing with a conflict. That is why we disallow `--merge` option in this case. `reset --keep` is meant to be used when removing some of the last
Hi Junio,
Quoted 9 lines · Junio C Hamano
Quoted 3 lines · Denton Liu
git-reset.txt contained a missing "a" and "wrt". Fix the missing "a" for correctness and replace "wrt" with "with respect to" so that the documentation is not so cryptic.
Could you try again without unrelated reflowing of the text?
Thanks.
Should reflowing the text be done in a separate patch or should it just not be done at all and just be considered noise?
Thanks,
Denton
Quoted 2 lines · Denton Liu
Should reflowing the text be done in a separate patch or should it just not be done at all and just be considered noise?
Of course when the rewrite is so extensive that the two versions of the whole paragraph needs to be carefully read and compared to judge if the change is desirable, reflowing of the paragraph would not waste reviewer's time trying to spot where the change is and also trying to verify there is no other change, and in such a case, reflowing would be very much OK.
For this particular case, however, I would say it is the latter, as the way I would have done it would look like either of these, which would not leave the result any harder to read with unnaturally uneven lines.
Thanks.
(variant #1)
Documentation/git-reset.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/git-reset.txt +2 -2
@@ -428,8 +428,8 @@ working index HEAD target working index HEAD `reset --merge` is meant to be used when resetting out of a conflicted merge. Any mergy operation guarantees that the working tree file that is -involved in the merge does not have local change wrt the index before -it starts, and that it writes the result out to the working tree. So if +involved in the merge does not have a local change with respect to the index +before it starts, and that it writes the result out to the working tree. So if we see some difference between the index and the target and also between the index and the working tree, then it means that we are not resetting out from a state that a mergy operation left after failing
(variant #2)
Documentation/git-reset.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
Documentation/git-reset.txt +2 -1
@@ -428,7 +428,8 @@ working index HEAD target working index HEAD `reset --merge` is meant to be used when resetting out of a conflicted merge. Any mergy operation guarantees that the working tree file that is -involved in the merge does not have local change wrt the index before +involved in the merge does not have a local change with respect to +the index before it starts, and that it writes the result out to the working tree. So if we see some difference between the index and the target and also between the index and the working tree, then it means that we are not
PATCH v2 1/1 git-reset.txt: clarify documentation
In reply to Denton Liugit-reset.txt contained a missing "a" and "wrt". Fix the missing "a" for correctness and replace "wrt" with "with respect to" so that the documentation is not so cryptic.
---
My mistake, I fired off the email before it was ready.
--- Documentation/git-reset.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
Documentation/git-reset.txt +2 -1
@@ -428,7 +428,8 @@ working index HEAD target working index HEAD `reset --merge` is meant to be used when resetting out of a conflicted merge. Any mergy operation guarantees that the working tree file that is -involved in the merge does not have local change wrt the index before +involved in the merge does not have a local change with respect to +the index before it starts, and that it writes the result out to the working tree. So if we see some difference between the index and the target and also between the index and the working tree, then it means that we are not
Signature · 1 line
2.21.0.260.g8f7229c82f