On Wed, Mar 3, 2010 at 09:55, Markus Elfring <Markus.Elfring@xxxxxx> wrote: >> Traditionally the right way to do this has been to make a temporary commit >> on the branch, i.e. > > I would like to avoid such commits for unfinished content updates. Should the > storage operation be provided by the stash instead for intermediate work results? > Will it happen to forget corresponding clean-up for "temporary" changes that > might be committed too early just to get them stored? Junio, I'm not sure how often WIP commits become accidentally published or left in the history, but perhaps it would be advantageous to provide a means of specifying officially that a particular commit is in fact a WIP commit such that no other commits can be made on top of this WIP commit and it can't be merged with other branches or pushed or whatever. -- 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