From: "Martin Ågren" <martin.agren@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Philippe Blain via GitGitGadget <gitgitgadget@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Gustaf Hendeby <hendeby@isy.liu.se>,
Philippe Blain <levraiphilippeblain@gmail.com>
Subject: Re: [PATCH] gitmodules.txt: fix 'GIT_WORK_TREE' variable name
Date: Sun, 3 Jan 2021 09:34:34 +0100 [thread overview]
Message-ID: <CAN0heSq8Hkq43mn06o_vxQD_FW3zSg5YSFDAtuONsFAvbNiNuA@mail.gmail.com> (raw)
In-Reply-To: <5ff0ef1332a66_a76d2086d@natae.notmuch>
On Sat, 2 Jan 2021 at 23:09, Felipe Contreras
<felipe.contreras@gmail.com> wrote:
>
> Martin Ågren wrote:
> > Good catch! I wonder what we should conclude from this having gone
> > unreported for so long.
>
> That perhaps not that many people actually read the official
> documentation?
>
> I've noticed the common response RTFM is not that common anymore. A lot
> of people seem to rely on Stack Overflow, blogs, and some semi-official
> documentation (GitHub, Atlassian, etc.).
Hmm, now that you say it, I think that matches my impression. There was
a time when that seemed to be a really "in" answer, if not always
entirely friendly. You're right that it seems to be quite a bit less
common today.
Martin
next prev parent reply other threads:[~2021-01-03 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-02 19:37 [PATCH] gitmodules.txt: fix 'GIT_WORK_TREE' variable name Philippe Blain via GitGitGadget
2021-01-02 21:34 ` Martin Ågren
2021-01-02 22:09 ` Felipe Contreras
2021-01-03 8:34 ` Martin Ågren [this message]
2021-01-03 0:33 ` Philippe Blain
2021-01-03 17:42 ` [PATCH v2] " Philippe Blain via GitGitGadget
2021-01-03 20:15 ` Martin Ågren
2021-01-06 6:05 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAN0heSq8Hkq43mn06o_vxQD_FW3zSg5YSFDAtuONsFAvbNiNuA@mail.gmail.com \
--to=martin.agren@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=hendeby@isy.liu.se \
--cc=levraiphilippeblain@gmail.com \
/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.
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 NNTP newsgroup(s).