[Libre-soc-dev] git.libre-soc.org mesa repo branch

[Luke Kenneth Casson Leighton]

On Thu, Sep 10, 2020 at 12:49 PM Hendrik Boom <hendrik at topoi.pooq.com> wrote:

> The developers of monotone, another distributed revision control
> system, recommend making a branch for every bug, and pushing it to
> any central repositories early in the process, before it's even
> debugged.  That way anyone in the project can look at it and offer
> reviews and advice.  This does mean a lot of short-term named
> branches, but a problem with a not-yet-tested fix wont shut
> anyone else out of their work.

i totally get it.  it's basically the "github" way of working (github
is based around "Pull Requests" which can only be done through
branches.   see below about that).

this works extremely well for products that are on an "incremental
development cycle".  where it falls down is where the product is on a
"rapid development and prototyping cycle".

> > to give you an example of why committing and pushing is so important: only
> > last week i lost git commits not once but TWICE due to a faulty laptop PSU.
>
> Feeling free to push early to a branch without fear of
> interfering with others' work would make this less likely.

i've done this before: it resulted not in review and collaboration but
in total isolation and, ultimately, made months to literally years of
work utterly pointless because the branch was completely and utterly
ignored.

the lesson that i learned is that it is better for people to stop
seeing it as "fear of interference" and to instead view it as being a
necessary and beneficial *need* for the team to communicate and
ultimately learn to collaborate and work together.

l.