From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Martin Ågren" <martin.agren@gmail.com>, git@vger.kernel.org
Cc: "Derrick Stolee" <dstolee@microsoft.com>,
"Taylor Blau" <me@ttaylorr.com>,
"Dr . Adam Nielsen" <admin@in-ici.net>,
"Jakub Narębski" <jnareb@gmail.com>
Subject: Re: [PATCH 0/3] Documentation: change "folder" to "directory"
Date: Mon, 25 Oct 2021 16:19:18 +0700 [thread overview]
Message-ID: <481447f9-7222-d9fc-269f-2de50299fb09@gmail.com> (raw)
In-Reply-To: <cover.1635094161.git.martin.agren@gmail.com>
On 25/10/21 00.09, Martin Ågren wrote:
> It is my understanding that we prefer "directory" over "folder" when
> discussing the file system concept. (Whereas "folder" is commonly used
> for the GUI view of such a directory, or for an IMAP folder.)
>
> I stumbled on a mention of the ".git folder" when going through the
> doc-diff between v2.33.0 and 9d530dc002 ("The fourteenth batch",
> 2021-10-18), and started looking around. This series is the outcome.
>
> Based on master.
>
> Martin Ågren (3):
> git-multi-pack-index.txt: change "folder" to "directory"
> gitignore.txt: change "folder" to "directory"
> gitweb.txt: change "folder" to "directory"
>
The same logical change over three patches, why aren't they be squashed
into single commit?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2021-10-25 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 17:09 [PATCH 0/3] Documentation: change "folder" to "directory" Martin Ågren
2021-10-24 17:09 ` [PATCH 1/3] git-multi-pack-index.txt: " Martin Ågren
2021-10-24 17:09 ` [PATCH 2/3] gitignore.txt: " Martin Ågren
2021-10-24 17:09 ` [PATCH 3/3] gitweb.txt: " Martin Ågren
2021-10-25 9:19 ` Bagas Sanjaya [this message]
2021-10-26 6:02 ` [PATCH 0/3] Documentation: " Martin Ågren
2021-10-27 18:48 ` Junio C Hamano
2021-10-25 15:31 ` Derrick Stolee
2021-10-25 18:08 ` 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=481447f9-7222-d9fc-269f-2de50299fb09@gmail.com \
--to=bagasdotme@gmail.com \
--cc=admin@in-ici.net \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=martin.agren@gmail.com \
--cc=me@ttaylorr.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.
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).