Hi Michael,
On 03/11/2019 20:22, Michael wrote:
On 2019-11-03, at 8:28 AM, Philip Oakley <philipoakley@iee.email> wrote:
But you still need to control what gets merged into mainline or master, right?
If you change the management viewpoint from "control" (with all its baggage) to
"select" then it's a bit easier to see that the managers task got that bit easier (they
don't need to 'protect' the VCS 'master') and the coder's work balance got easier because they do
have access to a storage mechanism that works.
You're correct that there is selection of what gets merged, or in a PR
scenario, accepted as the new 'latest', and the golden repo (read only to
others usually) reflects the magic hash number of the latest and greatest.
Keep in mind: Anyone can publish "This is my version of this project".
Very true, and one of my key points about control (of one's local repo)
being distributed to the user, rather than having to depend on access to
a central repo.
That I can take someone else's project, and add my own tweak to it, and then my version
is just as "valid" as theirs, is both the strong and weak point of this system.
A generic user has to determine which of several different repositories has the
best version to use.
I'd argue, that for 'maintained', open source projects, there will be
notifications of the locations that the current master hash can be
obtained from, rather than getting from some arbitrary 'Joe random'..
But any coder can work with any repository as a starting point to base from.
And, you can merge work done by several different people, each in their own repository,
to combine into the "newest and bestest".
The issue is less "What's in master", and more "What's in Keybounce's master" vs "What's in Zek's
master", or "What's in Ubuntu's master" vs "What's in Red Hat's master".
In the collaborative context, it's true that you can take work from
those you trust (as opposed to Joe.deadbeef), and usually you can also
easily see what work they have added (diff's etc)
Linus's job, as I understand, is more a case of "blessing this version" than
anything else at this point. Which gets back to the question of selecting from the many
choices available. The rest of us rely on his ability to select from the many choices so
that we don't need to worry about studying all the differences.
True, however the original comparison was with those older VCS's that
used diff based recording, and my comparison was for VCS systems that
started in the engineering domain (which where the cause of all those
procedures and processes that are endemic in most 'central control' VCS
systems came from).
Hopefully were are strenuously agreeing here...
--
You received this message because you are subscribed to the Google Groups "Git for
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/git-users/ce59a884-0a69-fe7d-fe97-7fe183a0d113%40iee.email.
