This is another approach of the wip feature (and a good one because of the git native implementation). I used it before.
Unfortunately, I don't know why, sometimes my stash disappeared or because of a mistake, were applied to another branch than the original one.
Moreover, when you decide to go back to your working branch, you could forget (days after) that you created a stash.
With the above method, you'll be notified on your branch status, and be sure that your work will never be lost.
In the case you want to create a wip over another wip (which is very messy), I'm agree with you, stash with its history feature is the most efficient approach.
Achievements
56
Karma
6,089
Total ProTip Views
Charity
Fork and commit to someone's open source project in need
Mongoose
Have at least one original repo where Ruby is the dominant language
This is another approach of the wip feature (and a good one because of the git native implementation). I used it before.
Unfortunately, I don't know why, sometimes my stash disappeared or because of a mistake, were applied to another branch than the original one.
Moreover, when you decide to go back to your working branch, you could forget (days after) that you created a stash.
With the above method, you'll be notified on your branch status, and be sure that your work will never be lost.
In the case you want to create a wip over another wip (which is very messy), I'm agree with you, stash with its history feature is the most efficient approach.