Excerpts from Jakub Narebski's message of Sat Feb 04 14:45:53 -0500 2012: Hi Jakub, These items are as much about UI as anything else, I think. UI that better helps users to know the state of their commits and branches can only be a good thing. People that have used git for a while and are comfortable with it may not see the need/point of these, but I think they could both really help new users. > In Mercurial 2.1 there are three available phases: 'public' for > published commits, 'draft' for local un-published commits and > 'secret' for local un-published commits which are not meant to be > published. How do you envision such a feature in git? A 'draft' commit (or chain of commits) could be determined from the push matching definitions and then marked with simple decorations in log output...This would extend the ability of status to note that your are X commits ahead of foo. This would see any commit on a branch that would be pushed automatically decorated with a 'draft' status. > While default "push matching" behavior makes it possible to have > "secret" commits, being able to explicitly mark commits as not for > publishing might be a good idea also for Git. Do you see using configuration or convention to achieve this? For example, any branch named private/foo could, by convention, be un-pushable without a force option? Alternately, a config item similar to the push matching stuff to allow the users to designate un-pushable branches could work too. Please don't take the above implementation possibilities as anything more than a starting point for discussion as they may be deeply flawed. I'm just tossing a few things out there as I think this is a good discussion to have. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 -- 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