IssueRaiser

> The obsession of git users with rewriting history has always puzzled me.

> The obsession of git users with rewriting history has always puzzled me. Editing draft commits is fine. Editing public commits is less fine. The problem is that git has no way to distinguish draft and public commits except by social convention. Mercurial Evolve actually enforces the separation between draft and public commits, and can also allow setting up servers where people can collaboratively edit draft commits. My talk about it: https://www.youtube.com/watch?v=4OlDm3akbqg

Posted by jordigh on Jun 19, 2015, 3:38 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.6,000 issues0 comments

hackernews (Other)

> The obsession of git users with rewriting history has always puzzled me.

jordighJun 19, 2015, 3:38 PM

> The obsession of git users with rewriting history has always puzzled me. Editing draft commits is fine. Editing public commits is less fine. The problem is that git has no way to distinguish draft and public commits except by social convention. Mercurial Evolve actually enforces the separation between draft and public commits, and can also allow setting up servers where people can collaboratively edit draft commits. My talk about it: https://www.youtube.com/watch?v=4OlDm3akbqg

Comments (0)

No comments yet. Start the discussion.

Comment on this issue