[Info-vax] Where to locate software

[Craig A. Berry]

On 6/16/16 4:24 AM, Johnny Billquist wrote:

> The distinction between committing and publishing on the other hand is
> not really anything that impress me. It's more a crutch for people who
> are afraid to commit.

People should be afraid to commit. They should review and revise their
code, make sure it passes tests, add more tests, reread and edit their
commit messages, think about the order and coherence of the commits
(changesets) and whether they preserve bisectability, all before
considering the code finished and ready to publish.

I had a professor in graduate school who joked that he'd spent
twenty-five years perfecting the skill of typing a clean first draft on
a typewriter but the advent of the word processor had ruined it all for
him. Resistance to local commits is pretty much the same attitude;
people have had to work a certain way because of the limitations of the
available tools, so tools without those limitations just feel wrong.

> But the talk about creating a changeset without contending with other
> users users changes more sounds like you have not understood branches.
>
> Or I could ask it this way: what contention???

I believe I said something up-thread about having to choose between a
branch per developer and a branch per feature. I guess you could have
one for each combination, in which case you can avoid contention. But
usually there is a feature or release branch with multiple people
working on it. And so to push your changes you have to stop what you're
working on and deal with any conflicting changes others have made right
then and there. Of course on very small teams, the contention may not
come up often enough to be worth bothering about.