git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, "René Scharfe" <l.s.r@web.de>,
	"Emily Shaffer" <emilyshaffer@google.com>,
	"Taylor Blau" <me@ttaylorr.com>, "Jeff King" <peff@peff.net>,
	"Felipe Contreras" <felipe.contreras@gmail.com>,
	"Jonathan Tan" <jonathantanmy@google.com>,
	"Bagas Sanjaya" <bagasdotme@gmail.com>
Subject: Re: What's cooking in git.git (Jun 2021, #07; Wed, 30)
Date: Fri, 02 Jul 2021 09:05:18 -0700	[thread overview]
Message-ID: <xmqqim1spupt.fsf@gitster.g> (raw)
In-Reply-To: <87tulcand1.fsf@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Fri, 02 Jul 2021 14:18:40 +0200")

Æ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.

>> 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.


  reply	other threads:[~2021-07-02 16:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30 22:55 What's cooking in git.git (Jun 2021, #07; Wed, 30) Junio C Hamano
2021-07-01  0:02 ` Felipe Contreras
     [not found] ` <CAFQ2z_PYJMzOBcN+KoQSfdD-eYtZVzrArL0Dh-YW-q3R8hgm2w@mail.gmail.com>
2021-07-01  7:19   ` Han-Wen Nienhuys
2021-07-01 13:06     ` Ævar Arnfjörð Bjarmason
2021-07-01 13:42 ` Ævar Arnfjörð Bjarmason
2021-07-01 14:20   ` Jeff Hostetler
2021-07-01 14:00 ` Ævar Arnfjörð Bjarmason
2021-07-01 15:21   ` Junio C Hamano
2021-07-02 12:18     ` Ævar Arnfjörð Bjarmason
2021-07-02 16:05       ` Junio C Hamano [this message]
2021-07-01 16:51   ` Jeff King
2021-07-01 16:20 ` Jeff King
2021-07-03  5:04 ` Elijah Newren
2021-07-05  8:03   ` Ævar Arnfjörð Bjarmason
2021-07-05 12:02     ` Jeff King
2021-07-06 13:46   ` Phillip Wood
2021-07-06 19:29     ` Ævar Arnfjörð Bjarmason
2021-07-06 20:36       ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqim1spupt.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=emilyshaffer@google.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jonathantanmy@google.com \
    --cc=l.s.r@web.de \
    --cc=me@ttaylorr.com \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).