threads / discuss / 60762

Suggestion for Git docummntation Book, Chapter "7.7 Git Tools - Reset Demystified"

Subject: Suggestion for Git docummntation Book, Chapter "7.7 Git Tools - Reset Demystified"

## tl;dr

2 messages between Jan 18, 2024 and Jan 20, 2024.

replies: 1people: 2as markdown or json

Peter Hunkeler· Jan 18, 2024, 18:42 UTC · lore
Hi,

I appreciate all the work that has been done to give us Git users good documentation.

As a rather-newbie I have to lookup the commands I need for rarely used, specific tasks. <git reset ...> being one of them. If find chapter "7.7 Git Tools - Reset Demystified" very helpful. There is however one point that newbies might not (yet) clearly understand: The git reset does *not* do anything to new, untracked files that might exist in the working tree. To cleanup, the advice from various places on the internet is to issue a "git clean -f -d" after the reset.

Maybe it would be helpful if said chapter had a short discussion about non tracked files, how to clean with "git clean -f -d"

Thanks Peter

Jeff King· Jan 20, 2024, 01:03 UTC · re: Peter Hunkeler · lore

Re: Suggestion for Git docummntation Book, Chapter "7.7 Git Tools - Reset Demystified"

On Thu, Jan 18, 2024 at 07:42:52PM +0100, Peter Hunkeler wrote:
Show 13 quoted lines
> I appreciate all the work that has been done to give us Git users good
> documentation.
> 
> As a rather-newbie I have to lookup the commands I need for rarely used,
> specific tasks. <git reset ...> being one of them. If find chapter "7.7
> Git Tools - Reset Demystified" very helpful. There is however one point
> that newbies might not (yet) clearly understand: The git reset does
> *not* do anything to new, untracked files that might exist in the
> working tree. To cleanup, the advice from various places on the internet
> is to issue a "git clean -f -d" after the reset.
> 
> Maybe it would be helpful if said chapter had a short discussion about
> non tracked files, how to clean with "git clean -f -d"

I don't think the folks who work on the book content tend to hang out on the development mailing list. You might get more response opening an issue in their GitHub repo:

  https://github.com/progit/progit2
-Peff

← back to recent threads