René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[7.7 Git Tools - Reset Demystified] - git reset with mode flag and pathspec","articleBody":"### General overview of your idea.\n\nThe section `Reset With a Path` illustrates the use of the reset command in the forms including a `\u003cpathspec>`. It reads well and the example is clear but there is [this snippet about the syntax](https://github.com/progit/progit2/blob/55081eaf0bfb4b0f9bab287c0dd035bf604e43bc/book/07-git-tools/sections/reset.asc?plain=1#L220) that I think might be slightly confusing:\n```\nThis form (since you did not specify a commit SHA-1 or branch, and you didn't specify `--soft` or `--hard`) is shorthand for `git reset --mixed HEAD file.txt`...\n```\nUsing `--soft` or `--hard` in this form would actually raise an error (which makes sense) but the current wording makes it sound like they could have been valid choices. I was surprised to see that `--mixed` is allowed (even if it triggers a deprecation warning) but I guess that this implementation detail is the reason why the [git-reset documentation](https://git-scm.com/docs/git-reset) does not explicitly preclude the use of a `\u003cmode>`  alongside a `\u003cpathspec>`.\n\nI can see why elaborations around `--mixed` were dropped there for the sake of clarity, so I think the snippet above would also become clearer if mentions to `\u003cmode>` were dropped altogether.\n\n\n\n### What problem will this solve?\n\nThe example in this section is good as it is, but some rephrasing would avoid potential confusion around mixing `\u003cmode>` with `\u003cpathspec>`, and also it would improve alignment between this section and the related documentation.\n\n### Have you thought about other solutions?\n\nI'd say it’s quite clear that the [git-reset documentation](https://git-scm.com/docs/git-reset) encourages the use of `\u003cmode>` only in the form:\n```\ngit reset [\u003cmode>] [-q] [\u003ccommit>]\n```\nwithout elaborating on the caveat that `--mixed` could be used beyond this case. \n\nIn the same spirit, I think that the snippet above could benefit from being rephrased to something along the lines of:\n```\nThis form (since you did not specify a commit SHA-1 or branch) is shorthand for `git reset HEAD -- file.txt`…\n```\nand perhaps adding a note with the caveat around `--mixed` if it's not too convoluted.\n\nWould this be worth a pull request? I know [a related issue](https://github.com/progit/progit2/issues/1187) was closed some years ago but in this case my point is not the warning when specifying `--mixed`.\n\n### Do you want to help with this enhancement idea?\n\nYes","author":{"url":"https://github.com/AlfaBetaBeta","@type":"Person","name":"AlfaBetaBeta"},"datePublished":"2025-04-30T22:21:17Z","url":"https://github.com/progit/progit2/issues/2031"}