Junio C Hamano wrote: > To stash is like putting something in /tmp on a system that runs a cron > job to clean out cruft from there once in a while. Another analogy is to > spitting an information out to syslog, so that it is kept until logs are > rotated. I like my analogy better. :) diff --git a/Documentation/git-stash.txt b/Documentation/git-stash.txt index baa4f55..119117e 100644 --- a/Documentation/git-stash.txt +++ b/Documentation/git-stash.txt @@ -17,7 +17,11 @@ DESCRIPTION Use 'git-stash' when you want to record the current state of the working directory and the index, but want to go back to a clean working directory. The command saves your local modifications away -and reverts the working directory to match the `HEAD` commit. +and reverts the working directory to match the `HEAD` commit. You should +think of the stash like a garbage can in which you place your temporary +work and then bring out to the curb. If you are quick to use your stashed +changes you can get them before garbage collection occurs (it's every +Tuesday where I live, but git does it every 30 days). The modifications stashed away by this command can be listed with `git-stash list`, inspected with `git-stash show`, and restored -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
