[Qt-creator] Creator segmentation faults becoming common...
Daniel Teske
daniel.teske at nokia.com
Tue Jul 7 17:56:30 CEST 2009
> Thats the thing... DVCS doesn't have the same notion of "commit" which lies at the heart of why SVN / CVS is broken / painful / bad. The idea is that one can publish to a separate repo or non-master branch but it doesn't get merged into "blessed" branch / repo until its been vetted. The model moves from a central store with "controls" to one based on a "web of trust"... the Qt community / Nokia identifies this branch... but other fixes can be made available by anyone at any time, tested, and easily backed out if necessary or, more importantly, incorporated when one synchronizes with the blessed branch.
>
> Take last weekend. There was a trivial bug which broke the build (needed a header file). Easy fix but the patch needed to be pushed around by pastebin because of this, um, somewhat broken use of git. The google tech talks by Linus and Schwarz (i recommend the latter) describe the development and dissemination model and the "web of trust". It has nothing to do with controlling dissemination, and everything to do with trusted branches and repos.
>
>
>
I don't think you need to tell us how git works. We are using git in a
way which best suits our requirements. As such we have decided to
automatically update gitorious/master with a 12h delay from our internal
master. This creates situations in which master does not build, and yet
the fix was already applied internally. That is obviously a drawback,
but we have decided that the benefits outweight the drawbacks.
git supports a lot of different work flows. While some recommend indeed
"web of trust", to claim that is the "right" way to use the tool and
claim that other usages are "broken" is simply wrong. In fact one of
strengths why we choose git over other version control systems was, that
we could implement a work flow which fits our requirements.
daniel
More information about the Qt-creator-old
mailing list