On Mon, Jun 12, 2017 at 11:42:44PM -0400, liam Beguin wrote: [...] >> Conceptually, the contents of the stash are *not* commits, even >> though the implementation happens to use a commit to represent each >> stash entry. Perhaps "has %d entry/entries" is an improvement, but >> a quick scanning of an early part of "git stash --help" tells me >> that > > what's different between a stash and a commit?
The same that exists between an interface and a concrete implementation in a programming language. "A stash entry" is a concept which is defined to keep explicitly recorded untracked files and which can be applied, shown and deleted from the stash bag (well, you can create a branch off it as well). The fact a stash entry is a merge commit of two synthetic commits is an implementation detail. It can be very useful at times for power users, but regular Git users need not be concerned with this. Another fact worth reiterating that what the UI displays to the user is better to match what the user reads in the docs. ;-)
