From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Martin Ågren" <martin.agren@gmail.com>,
"Philippe Blain via GitGitGadget" <gitgitgadget@gmail.com>
Cc: 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: Sat, 02 Jan 2021 16:09:23 -0600 [thread overview]
Message-ID: <5ff0ef1332a66_a76d2086d@natae.notmuch> (raw)
In-Reply-To: <CAN0heSqC3K6pJOr2ztz56+ZpKaMomA28rc4W5x8n0cC3K-rVgQ@mail.gmail.com>
Martin Ågren wrote:
> On Sat, 2 Jan 2021 at 20:39, Philippe Blain via GitGitGadget
> <gitgitgadget@gmail.com> wrote:
> >
> > From: Philippe Blain <levraiphilippeblain@gmail.com>
> >
> > 'gitmodules.txt' is a guide about the '.gitmodules' file that describes
> > submodules properties, and that file must exist at the root of the
> > repository. This was clarified in e5b5c1d2cf (Document clarification:
> > gitmodules, gitattributes, 2008-08-31).
> >
> > However, that commit mistakenly uses the non-existing environment
> > variable 'GIT_WORK_DIR' to refer to the root of the repository.
>
> 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.).
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2021-01-02 22:10 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 [this message]
2021-01-03 8:34 ` Martin Ågren
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=5ff0ef1332a66_a76d2086d@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=hendeby@isy.liu.se \
--cc=levraiphilippeblain@gmail.com \
--cc=martin.agren@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).