-
Notifications
You must be signed in to change notification settings - Fork 2k
Undoing things: Clarify what "git checkout" does to local files #1179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The current explanation of "git checkout -- <file>" seems a bit vague, so expand on it ever so slightly. Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Nice, thanks! |
Maybe I'm being unnecessarily picky, because the meaning is clear, but 'over top of' sounds odd to me. Certainly 'on top of' is the more common idiom—but in the case of copying, the old wording, 'copy over', seems to be the most common. But like I said, the meaning is still clear. I don't find 'copy over' vague, but if it does add clarity for others I'd say it's worth a little awkwardness. (P.S. I don't know if people usually comment on pull requests after they're merged? My bad if I should've opened an issue or something.) ETA: I just realized that 'copy over' can also mean 'copy from one thing to another', and that was probably your concern. Now that I think about it, what about getting rid of the word 'copy' altogether and using 'replace' instead? |
I'd agree that it isn't that common, and it definitely feels a bit odd to me saying it out loud, but it does get the point across, and I don't think anybody will misread that passage to mean something else. Do you want to submit a PR so we can see what it looks like? |
@HonkingGoose Which issue are you talking about? |
Hi @aollier,
It seems that both those things are now Edit: @aollier I was mistaken, this comment is not about a (new) issue but about this Pull-Request, I was thinking that I was commenting in a issue-report, instead of commenting in a Pull-Request. Sorry for confusing things! 😟 |
@HonkingGoose Good. Furthermore, if you work on Windows and are using TortoiseGit, you can see the issue related to the commit if the commit contains one of the keywords followed by # followed by the issue ID thanks to #1127. |
My commit message for PR #1246 was ambiguous. You'd usually be right to assume I was referencing an issue, not a different pull request. I've edited the commit message to clarify. |
The current explanation of "git checkout -- " seems a bit
vague, so expand on it ever so slightly.
Signed-off-by: Robert P. J. Day rpjday@crashcourse.ca