{"thread":{"id":"18903","subject":"[PATCH] git-commit.txt: Reword the description of git commit.","startedAt":"2009-04-16T16:59:34Z","lastAt":"2009-04-18T10:11:23Z","messageCount":2,"participants":["Matthieu Moy","Nanako Shiraishi"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"111461","messageId":"1239901174-30072-1-git-send-email-Matthieu.Moy@imag.fr","threadId":"18903","inReplyTo":null,"subject":"[PATCH] git-commit.txt: Reword the description of git commit.","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2009-04-16T16:59:34Z","receivedAt":"2009-04-16T16:59:34Z","isPatch":true,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"\"Record changes\" insists on recording the _delta_ between the parent\ncommit and the new revision, which can be mis-leading, since Git is\nreally snapshot-oriented. The new wording may be less misleading.\n---\nI'm actually resurecting a new thread :\n\nhttp://thread.gmane.org/gmane.comp.version-control.git/68647/focus=68823\n\nwhere a user was not understanding why custom diff drivers were not\nused by \"commit\" to tell whether the tree had changed (\"I keep doing\ngit diff's and it says there is no difference, but then git commit\nkeeps telling me there is\").\n\n Documentation/git-commit.txt |    2 +-\n 1 files changed, 1 insertions(+), 1 deletions(-)\n\ndiff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt\nindex b5d81be..c7f728f 100644\n--- a/Documentation/git-commit.txt\n+++ b/Documentation/git-commit.txt\n@@ -3,7 +3,7 @@ git-commit(1)\n \n NAME\n ----\n-git-commit - Record changes to the repository\n+git-commit - Record a new revision in the repository\n \n SYNOPSIS\n --------\n-- \n1.6.2.2.449.g92961.dirty\n"},{"id":"111568","messageId":"20090418191123.6117@nanako3.lavabit.com","threadId":"18903","inReplyTo":"1239901174-30072-1-git-send-email-Matthieu.Moy@imag.fr","subject":"Re: [PATCH] git-commit.txt: Reword the description of git commit.","fromName":"Nanako Shiraishi","fromEmail":"nanako3@lavabit.com","sentAt":"2009-04-18T10:11:23Z","receivedAt":"2009-04-18T10:11:23Z","isPatch":true,"sender":{"key":"nanako3@lavabit.com","avatar":"https://gravatar.com/avatar/3777b9e201c5883a62b1a6fdf7c53f2d712d1d80989146063ea861e33aad72a8?d=mp&s=160"},"body":"Quoting Matthieu Moy <Matthieu.Moy@imag.fr> writes:\n\n> \"Record changes\" insists on recording the _delta_ between the parent\n> commit and the new revision, which can be mis-leading, since Git is\n> really snapshot-oriented. The new wording may be less misleading.\n> ...\n> diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt\n> index b5d81be..c7f728f 100644\n> --- a/Documentation/git-commit.txt\n> +++ b/Documentation/git-commit.txt\n> @@ -3,7 +3,7 @@ git-commit(1)\n>  \n>  NAME\n>  ----\n> -git-commit - Record changes to the repository\n> +git-commit - Record a new revision in the repository\n\nI don't think this is a good change.\n\nWhen new people who don't know git yet are looking at output from git-help command in order to find what command they want to try, the original text requires them to know what \"repository\" means, but the new description forces them to know also what a revision is.\n\nI also think the original text is technically more correct. git-commit\ncommand does two things at the same time. It\n\n1) creates a new commit object (a.k.a revision)\n2) updates the HEAD pointer to the new commit object\n\nYour new wording expresses only the first part. Because it updates the HEAD, the end user perceives the difference between the commit previously pointed by HEAD and the new commit as recorded.\n\n-- \nNanako Shiraishi\nhttp://ivory.ap.teacup.com/nanako3/\n"}]}