git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Jun 2021, #07; Wed, 30)

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 2, 2021, 16:05 UTC
Message-ID
<xmqqim1spupt.fsf@gitster.g>
In-Reply-To
<87tulcand1.fsf@evledraar.gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> Yes, they can't be advanced separately, one depends on the other in
> turn. I'm suggesting that the parts that go earlier in the sequence
> could advance before the later parts.

Yes, as long as the bottom half is more stable and ready than the top half. When I queued these topics, however, I didn't get that impression. After all, if we have to replace the bottom half as often as the top half, having to maintain two topic branches is a needless chore.

Show 15 quoted lines
>> I actually do agree with the objection that www-data is a contrived
>> thing to use in the examples, not because the user www-data is
>> distro specific, but because it involves one physical human user
>> acting on two accounts, instead of two human users interacting with
>> each other.
>
> The www-thing is arbitrary, and I can change that bit, but what do you
> think of what I mentioned at the end of [2], i.e.:
>
>     
>     [...] the purposes of the example in the guide replacing Alice & Bob
>     with You & another version of you removes a lot of potential
>     confusion, we don't need to cover permissions, the other user doing
>     unexpected things like non-ff updates, pruning branches you may have
>     relied on through the --local clone etc.
www-data requiring more privilege than you do require permissions.

I still think two distinct human users coorporating towards the same goal would make easier-to-follow sample sessions. IOW, ...

>     It's implicit that both "users" are you, so we only have to discuss the
>     point of the actual example, how to pull and push between two different
>     repos, the "different users" in this case was always a distraction.

... my view of the presence of two distinct human users in the example is completely opposite from yours---to explain Git as a platform for inter-developer coordination, it is a crucial part, not a distraction, to have them as two separate human beings. It is OK to pretend, while practicing, that you who are typing to this window ares playing the role of Tom and you in the other window are playing the role of Mary, and that would be what learners would do, but the scenario the learners learn from should resemble more what they would do in the real world when they become fluent for the learning experience to be more useful and lasting in their minds., I would expect.

Thanks.
Previous: Ævar Arnfjörð BjarmasonNext: Jeff King
Message 8 of 18 in “What's cooking in git.git (Jun 2021, #07; Wed, 30)”
  1. Junio C HamanoJun 30, 2021
  2. Felipe ContrerasJul 1, 2021
  3. Ævar Arnfjörð BjarmasonJul 1, 2021
  4. Jeff HostetlerJul 1, 2021
  5. Ævar Arnfjörð BjarmasonJul 1, 2021
  6. Junio C HamanoJul 1, 2021
  7. Ævar Arnfjörð BjarmasonJul 2, 2021
  8. Junio C HamanoJul 2, 2021
  9. Jeff KingJul 1, 2021
  10. Jeff KingJul 1, 2021
  11. Elijah NewrenJul 3, 2021
  12. Ævar Arnfjörð BjarmasonJul 5, 2021
  13. Jeff KingJul 5, 2021
  14. Phillip WoodJul 6, 2021
  15. Ævar Arnfjörð BjarmasonJul 6, 2021
  16. Junio C HamanoJul 6, 2021
  17. Han-Wen NienhuysJul 1, 2021
  18. Ævar Arnfjörð BjarmasonJul 1, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.