{"thread":{"id":"47901","subject":"[PATCH v3 2/2] Replace non-ASCII apostrophes to ASCII single quotes in gitsubmodules.txt","startedAt":"2018-02-22T08:52:33Z","lastAt":"2018-02-22T20:42:11Z","messageCount":7,"participants":["marmot1123","Stefan Beller","Junio C Hamano"],"isPatch":true,"patchVersion":3,"patchTotal":2},"messages":[{"id":"339911","messageId":"01020161bcb6b3db-dd4dc2a0-4426-4bf0-97f3-18b299d91400-000000@eu-west-1.amazonses.com","threadId":"47901","inReplyTo":"01020161bcb6b2b5-6a915ec6-57e5-4619-b281-0e2a193c69a2-000000@eu-west-1.amazonses.com","subject":"[PATCH v3 2/2] Replace non-ASCII apostrophes to ASCII single quotes in gitsubmodules.txt","fromName":"marmot1123","fromEmail":"marmot.motoki@gmail.com","sentAt":"2018-02-22T08:52:25Z","receivedAt":"2018-02-22T08:52:33Z","isPatch":true,"sender":{"key":"marmot.motoki@gmail.com","avatar":"https://avatars.githubusercontent.com/u/6357126?v=4"},"body":"Before this patch, there are several non-ASCII apostrophes in\ngitsubmodules.txt, and misconverged at the https://git-scm.com/docs/gitsubmodules/ .\nTo make codes consistent, these non-ASCII apostrophes are replaced\nwith ASCII single quotes.  This patch also makes the document readable\non the website.\n\nSigned-off-by: Motoki Seki <marmot.motoki@gmail.com>\n---\n Documentation/gitsubmodules.txt | 10 +++++-----\n 1 file changed, 5 insertions(+), 5 deletions(-)\n\ndiff --git a/Documentation/gitsubmodules.txt b/Documentation/gitsubmodules.txt\nindex 0d59ab4cdfb1c..030c974c25606 100644\n--- a/Documentation/gitsubmodules.txt\n+++ b/Documentation/gitsubmodules.txt\n@@ -132,27 +132,27 @@ using older versions of Git.\n +\n It is possible to construct these old form repositories manually.\n +\n-When deinitialized or deleted (see below), the submodule’s Git\n+When deinitialized or deleted (see below), the submodule's Git\n directory is automatically moved to `$GIT_DIR/modules/<name>/`\n of the superproject.\n \n  * Deinitialized submodule: A `gitlink`, and a `.gitmodules` entry,\n-but no submodule working directory. The submodule’s git directory\n+but no submodule working directory. The submodule's git directory\n may be there as after deinitializing the git directory is kept around.\n The directory which is supposed to be the working directory is empty instead.\n +\n A submodule can be deinitialized by running `git submodule deinit`.\n Besides emptying the working directory, this command only modifies\n-the superproject’s `$GIT_DIR/config` file, so the superproject’s history\n+the superproject's `$GIT_DIR/config` file, so the superproject's history\n is not affected. This can be undone using `git submodule init`.\n \n  * Deleted submodule: A submodule can be deleted by running\n `git rm <submodule path> && git commit`. This can be undone\n using `git revert`.\n +\n-The deletion removes the superproject’s tracking data, which are\n+The deletion removes the superproject's tracking data, which are\n both the `gitlink` entry and the section in the `.gitmodules` file.\n-The submodule’s working directory is removed from the file\n+The submodule's working directory is removed from the file\n system, but the Git directory is kept around as it to make it\n possible to checkout past commits without requiring fetching\n from another repository.\n\n--\nhttps://github.com/git/git/pull/459\n"},{"id":"339912","messageId":"01020161bcb6b2b5-6a915ec6-57e5-4619-b281-0e2a193c69a2-000000@eu-west-1.amazonses.com","threadId":"47901","inReplyTo":"01020161b30b99df-5029ec2b-a5cb-475b-b54f-9879a117a7f3-000000@eu-west-1.amazonses.com","subject":"[PATCH v3 1/2] Fix misconversion of gitsubmodule.txt","fromName":"marmot1123","fromEmail":"marmot.motoki@gmail.com","sentAt":"2018-02-22T08:52:25Z","receivedAt":"2018-02-22T08:52:36Z","isPatch":true,"sender":{"key":"marmot.motoki@gmail.com","avatar":"https://avatars.githubusercontent.com/u/6357126?v=4"},"body":"In the 2nd and 4th paragraph of DESCRIPTION, there ware misconversions `submodule’s`.\nIt seems non-ASCII apostrophes, so I rewrite ASCII apostrophes.\n\nSigned-off-by: Motoki Seki <marmot.motoki@gmail.com>\n---\n Documentation/gitsubmodules.txt | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/gitsubmodules.txt b/Documentation/gitsubmodules.txt\nindex 46cf120f666df..0d59ab4cdfb1c 100644\n--- a/Documentation/gitsubmodules.txt\n+++ b/Documentation/gitsubmodules.txt\n@@ -24,7 +24,7 @@ On the filesystem, a submodule usually (but not always - see FORMS below)\n consists of (i) a Git directory located under the `$GIT_DIR/modules/`\n directory of its superproject, (ii) a working directory inside the\n superproject's working directory, and a `.git` file at the root of\n-the submodule’s working directory pointing to (i).\n+the submodule's working directory pointing to (i).\n \n Assuming the submodule has a Git directory at `$GIT_DIR/modules/foo/`\n and a working directory at `path/to/bar/`, the superproject tracks the\n@@ -33,7 +33,7 @@ in its `.gitmodules` file (see linkgit:gitmodules[5]) of the form\n `submodule.foo.path = path/to/bar`.\n \n The `gitlink` entry contains the object name of the commit that the\n-superproject expects the submodule’s working directory to be at.\n+superproject expects the submodule's working directory to be at.\n \n The section `submodule.foo.*` in the `.gitmodules` file gives additional\n hints to Gits porcelain layer such as where to obtain the submodule via\n\n--\nhttps://github.com/git/git/pull/459\n"},{"id":"339939","messageId":"CAGZ79kYLtXJZA865DS2JRi1RRw_L0t=f1iKJzvN+Uyroeg-pbw@mail.gmail.com","threadId":"47901","inReplyTo":"01020161bcb6b2b5-6a915ec6-57e5-4619-b281-0e2a193c69a2-000000@eu-west-1.amazonses.com","subject":"Re: [PATCH v3 1/2] Fix misconversion of gitsubmodule.txt","fromName":"Stefan Beller","fromEmail":"sbeller@google.com","sentAt":"2018-02-22T18:38:00Z","receivedAt":"2018-02-22T18:38:07Z","isPatch":true,"sender":{"key":"stefanbeller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/455868?v=4"},"body":"On Thu, Feb 22, 2018 at 12:52 AM, marmot1123 <marmot.motoki@gmail.com> wrote:\n> In the 2nd and 4th paragraph of DESCRIPTION, there ware misconversions `submodule’s`.\n> It seems non-ASCII apostrophes, so I rewrite ASCII apostrophes.\n>\n> Signed-off-by: Motoki Seki <marmot.motoki@gmail.com>\n> ---\n>  Documentation/gitsubmodules.txt | 4 ++--\n>  1 file changed, 2 insertions(+), 2 deletions(-)\n>\n> diff --git a/Documentation/gitsubmodules.txt b/Documentation/gitsubmodules.txt\n> index 46cf120f666df..0d59ab4cdfb1c 100644\n> --- a/Documentation/gitsubmodules.txt\n> +++ b/Documentation/gitsubmodules.txt\n> @@ -24,7 +24,7 @@ On the filesystem, a submodule usually (but not always - see FORMS below)\n>  consists of (i) a Git directory located under the `$GIT_DIR/modules/`\n>  directory of its superproject, (ii) a working directory inside the\n>  superproject's working directory, and a `.git` file at the root of\n> -the submodule’s working directory pointing to (i).\n> +the submodule's working directory pointing to (i).\n>\n>  Assuming the submodule has a Git directory at `$GIT_DIR/modules/foo/`\n>  and a working directory at `path/to/bar/`, the superproject tracks the\n> @@ -33,7 +33,7 @@ in its `.gitmodules` file (see linkgit:gitmodules[5]) of the form\n>  `submodule.foo.path = path/to/bar`.\n>\n>  The `gitlink` entry contains the object name of the commit that the\n> -superproject expects the submodule’s working directory to be at.\n> +superproject expects the submodule's working directory to be at.\n>\n>  The section `submodule.foo.*` in the `.gitmodules` file gives additional\n>  hints to Gits porcelain layer such as where to obtain the submodule via\n>\n> --\n> https://github.com/git/git/pull/459\n"},{"id":"339968","messageId":"xmqqy3jkvkr9.fsf@gitster-ct.c.googlers.com","threadId":"47901","inReplyTo":"CAGZ79kYLtXJZA865DS2JRi1RRw_L0t=f1iKJzvN+Uyroeg-pbw@mail.gmail.com","subject":"Re: [PATCH v3 1/2] Fix misconversion of gitsubmodule.txt","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2018-02-22T20:20:58Z","receivedAt":"2018-02-22T20:21:05Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Stefan Beller <sbeller@google.com> writes:\n\n> On Thu, Feb 22, 2018 at 12:52 AM, marmot1123 <marmot.motoki@gmail.com> wrote:\n>> In the 2nd and 4th paragraph of DESCRIPTION, there ware misconversions `submodule’s`.\n>> It seems non-ASCII apostrophes, so I rewrite ASCII apostrophes.\n>>\n>> Signed-off-by: Motoki Seki <marmot.motoki@gmail.com>\n>> ---\n>>  Documentation/gitsubmodules.txt | 4 ++--\n>>  1 file changed, 2 insertions(+), 2 deletions(-)\n>>\n>> diff --git a/Documentation/gitsubmodules.txt b/Documentation/gitsubmodules.txt\n>> index 46cf120f666df..0d59ab4cdfb1c 100644\n>> --- a/Documentation/gitsubmodules.txt\n>> +++ b/Documentation/gitsubmodules.txt\n>> @@ -24,7 +24,7 @@ On the filesystem, a submodule usually (but not always - see FORMS below)\n>>  consists of (i) a Git directory located under the `$GIT_DIR/modules/`\n>>  directory of its superproject, (ii) a working directory inside the\n>>  superproject's working directory, and a `.git` file at the root of\n>> -the submodule’s working directory pointing to (i).\n>> +the submodule's working directory pointing to (i).\n>>\n>>  Assuming the submodule has a Git directory at `$GIT_DIR/modules/foo/`\n>>  and a working directory at `path/to/bar/`, the superproject tracks the\n>> @@ -33,7 +33,7 @@ in its `.gitmodules` file (see linkgit:gitmodules[5]) of the form\n>>  `submodule.foo.path = path/to/bar`.\n>>\n>>  The `gitlink` entry contains the object name of the commit that the\n>> -superproject expects the submodule’s working directory to be at.\n>> +superproject expects the submodule's working directory to be at.\n>>\n>>  The section `submodule.foo.*` in the `.gitmodules` file gives additional\n>>  hints to Gits porcelain layer such as where to obtain the submodule via\n>>\n>> --\n>> https://github.com/git/git/pull/459\n\nForgot to say something of your own?  Perhaps wanted to (1) show a\nsample of a better log message, (2) say \"Acked-by\", (3) re-raise the\npoint that the same \"error\" already appears in the same file and it\nis better to clean them up all at once, or (4) something else?\n\n\n\n"},{"id":"339970","messageId":"xmqqtvu8vkbo.fsf@gitster-ct.c.googlers.com","threadId":"47901","inReplyTo":"01020161bcb6b3db-dd4dc2a0-4426-4bf0-97f3-18b299d91400-000000@eu-west-1.amazonses.com","subject":"Re: [PATCH v3 2/2] Replace non-ASCII apostrophes to ASCII single quotes in gitsubmodules.txt","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2018-02-22T20:30:19Z","receivedAt":"2018-02-22T20:30:32Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"marmot1123 <marmot.motoki@gmail.com> writes:\n\n> Before this patch, there are several non-ASCII apostrophes in\n> gitsubmodules.txt, and misconverged at the https://git-scm.com/docs/gitsubmodules/ .\n> To make codes consistent, these non-ASCII apostrophes are replaced\n> with ASCII single quotes.  This patch also makes the document readable\n> on the website.\n>\n> Signed-off-by: Motoki Seki <marmot.motoki@gmail.com>\n> ---\n\nInteresting.  I didn't know the AsciiDoc renderer used there\nmishandled these non-ASCII ticks.  Thanks for writing it down in the\nlog message.\n\nWhen we say \"there are ...\" in a proposed commit log message\n(i.e. in the present tense), it is the norm to talk about the\ncurrent state of affairs, so \"Before this patch,\" is redundant.  I'd\ndrop it myself while queuing, and possibly applying other typofixes.\n\nThanks.\n\n\n>  Documentation/gitsubmodules.txt | 10 +++++-----\n>  1 file changed, 5 insertions(+), 5 deletions(-)\n>\n> diff --git a/Documentation/gitsubmodules.txt b/Documentation/gitsubmodules.txt\n> index 0d59ab4cdfb1c..030c974c25606 100644\n> --- a/Documentation/gitsubmodules.txt\n> +++ b/Documentation/gitsubmodules.txt\n> @@ -132,27 +132,27 @@ using older versions of Git.\n>  +\n>  It is possible to construct these old form repositories manually.\n>  +\n> -When deinitialized or deleted (see below), the submodule’s Git\n> +When deinitialized or deleted (see below), the submodule's Git\n>  directory is automatically moved to `$GIT_DIR/modules/<name>/`\n>  of the superproject.\n>  \n>   * Deinitialized submodule: A `gitlink`, and a `.gitmodules` entry,\n> -but no submodule working directory. The submodule’s git directory\n> +but no submodule working directory. The submodule's git directory\n>  may be there as after deinitializing the git directory is kept around.\n>  The directory which is supposed to be the working directory is empty instead.\n>  +\n>  A submodule can be deinitialized by running `git submodule deinit`.\n>  Besides emptying the working directory, this command only modifies\n> -the superproject’s `$GIT_DIR/config` file, so the superproject’s history\n> +the superproject's `$GIT_DIR/config` file, so the superproject's history\n>  is not affected. This can be undone using `git submodule init`.\n>  \n>   * Deleted submodule: A submodule can be deleted by running\n>  `git rm <submodule path> && git commit`. This can be undone\n>  using `git revert`.\n>  +\n> -The deletion removes the superproject’s tracking data, which are\n> +The deletion removes the superproject's tracking data, which are\n>  both the `gitlink` entry and the section in the `.gitmodules` file.\n> -The submodule’s working directory is removed from the file\n> +The submodule's working directory is removed from the file\n>  system, but the Git directory is kept around as it to make it\n>  possible to checkout past commits without requiring fetching\n>  from another repository.\n>\n> --\n> https://github.com/git/git/pull/459\n"},{"id":"339971","messageId":"CAGZ79kZMkuek_yVAfrTBz6jbeamc3JDjPg2JTnYb45tONAj1iQ@mail.gmail.com","threadId":"47901","inReplyTo":"xmqqy3jkvkr9.fsf@gitster-ct.c.googlers.com","subject":"Re: [PATCH v3 1/2] Fix misconversion of gitsubmodule.txt","fromName":"Stefan Beller","fromEmail":"sbeller@google.com","sentAt":"2018-02-22T20:36:40Z","receivedAt":"2018-02-22T20:36:47Z","isPatch":true,"sender":{"key":"stefanbeller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/455868?v=4"},"body":"On Thu, Feb 22, 2018 at 12:20 PM, Junio C Hamano <gitster@pobox.com> wrote:\n\n>\n> Forgot to say something of your own?  Perhaps wanted to (1) show a\n> sample of a better log message, (2) say \"Acked-by\", (3) re-raise the\n> point that the same \"error\" already appears in the same file and it\n> is better to clean them up all at once, or (4) something else?\n\n(2) Acked-by and (4) I-am-sorry-for.\n\nThanks,\nStefan\n"},{"id":"339973","messageId":"xmqqpo4wvjs4.fsf@gitster-ct.c.googlers.com","threadId":"47901","inReplyTo":"CAGZ79kZMkuek_yVAfrTBz6jbeamc3JDjPg2JTnYb45tONAj1iQ@mail.gmail.com","subject":"Re: [PATCH v3 1/2] Fix misconversion of gitsubmodule.txt","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2018-02-22T20:42:03Z","receivedAt":"2018-02-22T20:42:11Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Stefan Beller <sbeller@google.com> writes:\n\n> On Thu, Feb 22, 2018 at 12:20 PM, Junio C Hamano <gitster@pobox.com> wrote:\n>\n>>\n>> Forgot to say something of your own?  Perhaps wanted to (1) show a\n>> sample of a better log message, (2) say \"Acked-by\", (3) re-raise the\n>> point that the same \"error\" already appears in the same file and it\n>> is better to clean them up all at once, or (4) something else?\n>\n> (2) Acked-by and (4) I-am-sorry-for.\n\nOK, I think the two patches are better squashed into one; in the\nlarger picture, it really does not matter where the problem\noriginated from.\n\nHere is what I tentatively queued with copyedited log message.\n\n-- >8 --\nFrom: Motoki Seki <marmot.motoki@gmail.com>\nDate: Thu, 22 Feb 2018 08:52:25 +0000\nSubject: [PATCH] Documentation/gitsubmodules.txt: avoid non-ASCII apostrophes\n\nIn gitsubmodules.txt, a few non-ASCII apostrophes are used to spell\npossessive, e.g. \"submodule's\".  These unfortunately are not\nrendered at https://git-scm.com/docs/gitsubmodules correctly by the\nrenderer used there.\n\nUse ASCII apostrophes instead to work around the problem.  It also\nis good to be consistent, as there are possessives spelled with\nASCII apostrophes.\n\nSigned-off-by: Motoki Seki <marmot.motoki@gmail.com>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>\n---\n Documentation/gitsubmodules.txt | 14 +++++++-------\n 1 file changed, 7 insertions(+), 7 deletions(-)\n\ndiff --git a/Documentation/gitsubmodules.txt b/Documentation/gitsubmodules.txt\nindex 46cf120f66..030c974c25 100644\n--- a/Documentation/gitsubmodules.txt\n+++ b/Documentation/gitsubmodules.txt\n@@ -24,7 +24,7 @@ On the filesystem, a submodule usually (but not always - see FORMS below)\n consists of (i) a Git directory located under the `$GIT_DIR/modules/`\n directory of its superproject, (ii) a working directory inside the\n superproject's working directory, and a `.git` file at the root of\n-the submodule’s working directory pointing to (i).\n+the submodule's working directory pointing to (i).\n \n Assuming the submodule has a Git directory at `$GIT_DIR/modules/foo/`\n and a working directory at `path/to/bar/`, the superproject tracks the\n@@ -33,7 +33,7 @@ in its `.gitmodules` file (see linkgit:gitmodules[5]) of the form\n `submodule.foo.path = path/to/bar`.\n \n The `gitlink` entry contains the object name of the commit that the\n-superproject expects the submodule’s working directory to be at.\n+superproject expects the submodule's working directory to be at.\n \n The section `submodule.foo.*` in the `.gitmodules` file gives additional\n hints to Gits porcelain layer such as where to obtain the submodule via\n@@ -132,27 +132,27 @@ using older versions of Git.\n +\n It is possible to construct these old form repositories manually.\n +\n-When deinitialized or deleted (see below), the submodule’s Git\n+When deinitialized or deleted (see below), the submodule's Git\n directory is automatically moved to `$GIT_DIR/modules/<name>/`\n of the superproject.\n \n  * Deinitialized submodule: A `gitlink`, and a `.gitmodules` entry,\n-but no submodule working directory. The submodule’s git directory\n+but no submodule working directory. The submodule's git directory\n may be there as after deinitializing the git directory is kept around.\n The directory which is supposed to be the working directory is empty instead.\n +\n A submodule can be deinitialized by running `git submodule deinit`.\n Besides emptying the working directory, this command only modifies\n-the superproject’s `$GIT_DIR/config` file, so the superproject’s history\n+the superproject's `$GIT_DIR/config` file, so the superproject's history\n is not affected. This can be undone using `git submodule init`.\n \n  * Deleted submodule: A submodule can be deleted by running\n `git rm <submodule path> && git commit`. This can be undone\n using `git revert`.\n +\n-The deletion removes the superproject’s tracking data, which are\n+The deletion removes the superproject's tracking data, which are\n both the `gitlink` entry and the section in the `.gitmodules` file.\n-The submodule’s working directory is removed from the file\n+The submodule's working directory is removed from the file\n system, but the Git directory is kept around as it to make it\n possible to checkout past commits without requiring fetching\n from another repository.\n-- \n2.16.2-264-ge3a80781f5\n\n\n\n"}]}