✳flâneur — a map of the web's best reading

Git Can't Be Made Consistent - Bram Cohen's Journal — LiveJournal

bramcohen.livejournal.com · 659 words · saved by 1 readers

If this type of authorization does not work for you, convert your account using the link By logging in to LiveJournal using a third-party service you accept LiveJournal's User agreement Are we misunderstanding what you meant? Мыс Бринера и Ковш бухты Рудной Как не нужно делать, если у вас образовался долг по кредитке «У нас есть человек, который помечает всех обнажённых» «Наконец-то нормальная командировка» «Без сна» в МТЮЗе. О любви, преступлении, музыке и смерти Предрождественский Кипр. Прогулка Три портрета Надежды Половцовой и не только Новороссийский декабрь — почти март Продакт-плейсмент «Аэрофлота» в «Кавказской пленнице» Пакистан: Ларкана и Мохенджо-Д

28 Git Can't Be Made Consistent This post complains about Git lacking eventual consistency. I have a little secret for you: Git can't be made to have eventual consistency. Everybody seems to think the problem is a technical one, of complexity vs. simplicity of implementation. They're wrong. The problem is semantics. Git follows the semantics which you want 99% of the time, at the cost of having some edge cases which it's inherently just plain broken on. When you make a change in Git (and Mercurial) you're essentially making the following statement: This is the way things are now. Forget whatev

Explore this link on the map →

related reading