{"thread":{"id":"13329","subject":"[PATCH] Documentation: rename \"hooks.txt\" to \"githooks.txt\" and make it a man page","startedAt":"2008-04-30T06:08:20Z","lastAt":"2008-04-30T16:28:31Z","messageCount":3,"participants":["Christian Couder","Jakub Narebski","Manoj Srivastava"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"75640","messageId":"20080430080820.ef5a4c2a.chriscool@tuxfamily.org","threadId":"13329","inReplyTo":null,"subject":"[PATCH] Documentation: rename \"hooks.txt\" to \"githooks.txt\" and make it a man page","fromName":"Christian Couder","fromEmail":"chriscool@tuxfamily.org","sentAt":"2008-04-30T06:08:20Z","receivedAt":"2008-04-30T06:08:20Z","isPatch":true,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Also now \"gitcli(5)\" becomes \"gitcli(7)\".\n\nSigned-off-by: Christian Couder <chriscool@tuxfamily.org>\n---\n Documentation/Makefile     |    5 +-\n Documentation/gitcli.txt   |    2 +-\n Documentation/githooks.txt |  301 ++++++++++++++++++++++++++++++++++++++++++++\n Documentation/hooks.txt    |  285 -----------------------------------------\n 4 files changed, 304 insertions(+), 289 deletions(-)\n create mode 100644 Documentation/githooks.txt\n delete mode 100644 Documentation/hooks.txt\n\n\tHere is an example of what we could do to make more\n\tdocumentation available to \"git help\".\n\ndiff --git a/Documentation/Makefile b/Documentation/Makefile\nindex 43781fb..4144d1e 100644\n--- a/Documentation/Makefile\n+++ b/Documentation/Makefile\n@@ -2,8 +2,8 @@ MAN1_TXT= \\\n \t$(filter-out $(addsuffix .txt, $(ARTICLES) $(SP_ARTICLES)), \\\n \t\t$(wildcard git-*.txt)) \\\n \tgitk.txt\n-MAN5_TXT=gitattributes.txt gitignore.txt gitcli.txt gitmodules.txt\n-MAN7_TXT=git.txt\n+MAN5_TXT=gitattributes.txt gitignore.txt gitmodules.txt githooks.txt\n+MAN7_TXT=git.txt gitcli.txt\n \n MAN_TXT = $(MAN1_TXT) $(MAN5_TXT) $(MAN7_TXT)\n MAN_XML=$(patsubst %.txt,%.xml,$(MAN_TXT))\n@@ -18,7 +18,6 @@ ARTICLES += cvs-migration\n ARTICLES += diffcore\n ARTICLES += howto-index\n ARTICLES += repository-layout\n-ARTICLES += hooks\n ARTICLES += everyday\n ARTICLES += git-tools\n ARTICLES += glossary\ndiff --git a/Documentation/gitcli.txt b/Documentation/gitcli.txt\nindex 7ee5ce3..835cb05 100644\n--- a/Documentation/gitcli.txt\n+++ b/Documentation/gitcli.txt\n@@ -1,4 +1,4 @@\n-gitcli(5)\n+gitcli(7)\n =========\n \n NAME\ndiff --git a/Documentation/githooks.txt b/Documentation/githooks.txt\nnew file mode 100644\nindex 0000000..62ee065\n--- /dev/null\n+++ b/Documentation/githooks.txt\n@@ -0,0 +1,301 @@\n+githooks(5)\n+===========\n+\n+NAME\n+----\n+githooks - Hooks used by git\n+\n+SYNOPSIS\n+--------\n+$GIT_DIR/hooks/*\n+\n+\n+DESCRIPTION\n+-----------\n+\n+Hooks are little scripts you can place in `$GIT_DIR/hooks`\n+directory to trigger action at certain points.  When\n+`git-init` is run, a handful example hooks are copied in the\n+`hooks` directory of the new repository, but by default they are\n+all disabled.  To enable a hook, make it executable with `chmod +x`.\n+\n+This document describes the currently defined hooks.\n+\n+applypatch-msg\n+--------------\n+\n+This hook is invoked by `git-am` script.  It takes a single\n+parameter, the name of the file that holds the proposed commit\n+log message.  Exiting with non-zero status causes\n+`git-am` to abort before applying the patch.\n+\n+The hook is allowed to edit the message file in place, and can\n+be used to normalize the message into some project standard\n+format (if the project has one). It can also be used to refuse\n+the commit after inspecting the message file.\n+\n+The default 'applypatch-msg' hook, when enabled, runs the\n+'commit-msg' hook, if the latter is enabled.\n+\n+pre-applypatch\n+--------------\n+\n+This hook is invoked by `git-am`.  It takes no parameter,\n+and is invoked after the patch is applied, but before a commit\n+is made.  Exiting with non-zero status causes the working tree\n+after application of the patch not committed.\n+\n+It can be used to inspect the current working tree and refuse to\n+make a commit if it does not pass certain test.\n+\n+The default 'pre-applypatch' hook, when enabled, runs the\n+'pre-commit' hook, if the latter is enabled.\n+\n+post-applypatch\n+---------------\n+\n+This hook is invoked by `git-am`.  It takes no parameter,\n+and is invoked after the patch is applied and a commit is made.\n+\n+This hook is meant primarily for notification, and cannot affect\n+the outcome of `git-am`.\n+\n+pre-commit\n+----------\n+\n+This hook is invoked by `git-commit`, and can be bypassed\n+with `\\--no-verify` option.  It takes no parameter, and is\n+invoked before obtaining the proposed commit log message and\n+making a commit.  Exiting with non-zero status from this script\n+causes the `git-commit` to abort.\n+\n+The default 'pre-commit' hook, when enabled, catches introduction\n+of lines with trailing whitespaces and aborts the commit when\n+such a line is found.\n+\n+All the `git-commit` hooks are invoked with the environment\n+variable `GIT_EDITOR=:` if the command will not bring up an editor\n+to modify the commit message.\n+\n+prepare-commit-msg\n+------------------\n+\n+This hook is invoked by `git-commit` right after preparing the\n+default log message, and before the editor is started.\n+\n+It takes one to three parameters.  The first is the name of the file\n+that the commit log message.  The second is the source of the commit\n+message, and can be: `message` (if a `\\-m` or `\\-F` option was\n+given); `template` (if a `\\-t` option was given or the\n+configuration option `commit.template` is set); `merge` (if the\n+commit is a merge or a `.git/MERGE_MSG` file exists); `squash`\n+(if a `.git/SQUASH_MSG` file exists); or `commit`, followed by\n+a commit SHA1 (if a `\\-c`, `\\-C` or `\\--amend` option was given).\n+\n+If the exit status is non-zero, `git-commit` will abort.\n+\n+The purpose of the hook is to edit the message file in place, and\n+it is not suppressed by the `\\--no-verify` option.  A non-zero exit\n+means a failure of the hook and aborts the commit.  It should not\n+be used as replacement for pre-commit hook.\n+\n+The sample `prepare-commit-msg` hook that comes with git comments\n+out the `Conflicts:` part of a merge's commit message.\n+\n+commit-msg\n+----------\n+\n+This hook is invoked by `git-commit`, and can be bypassed\n+with `\\--no-verify` option.  It takes a single parameter, the\n+name of the file that holds the proposed commit log message.\n+Exiting with non-zero status causes the `git-commit` to\n+abort.\n+\n+The hook is allowed to edit the message file in place, and can\n+be used to normalize the message into some project standard\n+format (if the project has one). It can also be used to refuse\n+the commit after inspecting the message file.\n+\n+The default 'commit-msg' hook, when enabled, detects duplicate\n+\"Signed-off-by\" lines, and aborts the commit if one is found.\n+\n+post-commit\n+-----------\n+\n+This hook is invoked by `git-commit`.  It takes no\n+parameter, and is invoked after a commit is made.\n+\n+This hook is meant primarily for notification, and cannot affect\n+the outcome of `git-commit`.\n+\n+post-checkout\n+-----------\n+\n+This hook is invoked when a `git-checkout` is run after having updated the\n+worktree.  The hook is given three parameters: the ref of the previous HEAD,\n+the ref of the new HEAD (which may or may not have changed), and a flag\n+indicating whether the checkout was a branch checkout (changing branches,\n+flag=1) or a file checkout (retrieving a file from the index, flag=0).\n+This hook cannot affect the outcome of `git-checkout`.\n+\n+This hook can be used to perform repository validity checks, auto-display\n+differences from the previous HEAD if different, or set working dir metadata\n+properties.\n+\n+post-merge\n+-----------\n+\n+This hook is invoked by `git-merge`, which happens when a `git pull`\n+is done on a local repository.  The hook takes a single parameter, a status\n+flag specifying whether or not the merge being done was a squash merge.\n+This hook cannot affect the outcome of `git-merge`.\n+\n+This hook can be used in conjunction with a corresponding pre-commit hook to\n+save and restore any form of metadata associated with the working tree\n+(eg: permissions/ownership, ACLS, etc).  See contrib/hooks/setgitperms.perl\n+for an example of how to do this.\n+\n+[[pre-receive]]\n+pre-receive\n+-----------\n+\n+This hook is invoked by `git-receive-pack` on the remote repository,\n+which happens when a `git push` is done on a local repository.\n+Just before starting to update refs on the remote repository, the\n+pre-receive hook is invoked.  Its exit status determines the success\n+or failure of the update.\n+\n+This hook executes once for the receive operation. It takes no\n+arguments, but for each ref to be updated it receives on standard\n+input a line of the format:\n+\n+  <old-value> SP <new-value> SP <ref-name> LF\n+\n+where `<old-value>` is the old object name stored in the ref,\n+`<new-value>` is the new object name to be stored in the ref and\n+`<ref-name>` is the full name of the ref.\n+When creating a new ref, `<old-value>` is 40 `0`.\n+\n+If the hook exits with non-zero status, none of the refs will be\n+updated. If the hook exits with zero, updating of individual refs can\n+still be prevented by the <<update,'update'>> hook.\n+\n+Both standard output and standard error output are forwarded to\n+`git-send-pack` on the other end, so you can simply `echo` messages\n+for the user.\n+\n+[[update]]\n+update\n+------\n+\n+This hook is invoked by `git-receive-pack` on the remote repository,\n+which happens when a `git push` is done on a local repository.\n+Just before updating the ref on the remote repository, the update hook\n+is invoked.  Its exit status determines the success or failure of\n+the ref update.\n+\n+The hook executes once for each ref to be updated, and takes\n+three parameters:\n+\n+ - the name of the ref being updated,\n+ - the old object name stored in the ref,\n+ - and the new objectname to be stored in the ref.\n+\n+A zero exit from the update hook allows the ref to be updated.\n+Exiting with a non-zero status prevents `git-receive-pack`\n+from updating that ref.\n+\n+This hook can be used to prevent 'forced' update on certain refs by\n+making sure that the object name is a commit object that is a\n+descendant of the commit object named by the old object name.\n+That is, to enforce a \"fast forward only\" policy.\n+\n+It could also be used to log the old..new status.  However, it\n+does not know the entire set of branches, so it would end up\n+firing one e-mail per ref when used naively, though.  The\n+<<post-receive,'post-receive'>> hook is more suited to that.\n+\n+Another use suggested on the mailing list is to use this hook to\n+implement access control which is finer grained than the one\n+based on filesystem group.\n+\n+Both standard output and standard error output are forwarded to\n+`git-send-pack` on the other end, so you can simply `echo` messages\n+for the user.\n+\n+The default 'update' hook, when enabled--and with\n+`hooks.allowunannotated` config option turned on--prevents\n+unannotated tags to be pushed.\n+\n+[[post-receive]]\n+post-receive\n+------------\n+\n+This hook is invoked by `git-receive-pack` on the remote repository,\n+which happens when a `git push` is done on a local repository.\n+It executes on the remote repository once after all the refs have\n+been updated.\n+\n+This hook executes once for the receive operation.  It takes no\n+arguments, but gets the same information as the\n+<<pre-receive,'pre-receive'>>\n+hook does on its standard input.\n+\n+This hook does not affect the outcome of `git-receive-pack`, as it\n+is called after the real work is done.\n+\n+This supersedes the <<post-update,'post-update'>> hook in that it gets\n+both old and new values of all the refs in addition to their\n+names.\n+\n+Both standard output and standard error output are forwarded to\n+`git-send-pack` on the other end, so you can simply `echo` messages\n+for the user.\n+\n+The default 'post-receive' hook is empty, but there is\n+a sample script `post-receive-email` provided in the `contrib/hooks`\n+directory in git distribution, which implements sending commit\n+emails.\n+\n+[[post-update]]\n+post-update\n+-----------\n+\n+This hook is invoked by `git-receive-pack` on the remote repository,\n+which happens when a `git push` is done on a local repository.\n+It executes on the remote repository once after all the refs have\n+been updated.\n+\n+It takes a variable number of parameters, each of which is the\n+name of ref that was actually updated.\n+\n+This hook is meant primarily for notification, and cannot affect\n+the outcome of `git-receive-pack`.\n+\n+The 'post-update' hook can tell what are the heads that were pushed,\n+but it does not know what their original and updated values are,\n+so it is a poor place to do log old..new. The\n+<<post-receive,'post-receive'>> hook does get both original and\n+updated values of the refs. You might consider it instead if you need\n+them.\n+\n+When enabled, the default 'post-update' hook runs\n+`git-update-server-info` to keep the information used by dumb\n+transports (e.g., HTTP) up-to-date.  If you are publishing\n+a git repository that is accessible via HTTP, you should\n+probably enable this hook.\n+\n+Both standard output and standard error output are forwarded to\n+`git-send-pack` on the other end, so you can simply `echo` messages\n+for the user.\n+\n+pre-auto-gc\n+-----------\n+\n+This hook is invoked by `git-gc --auto`. It takes no parameter, and\n+exiting with non-zero status from this script causes the `git-gc --auto`\n+to abort.\n+\n+GIT\n+---\n+Part of the linkgit:git[7] suite\ndiff --git a/Documentation/hooks.txt b/Documentation/hooks.txt\ndeleted file mode 100644\nindex 44fbe58..0000000\n--- a/Documentation/hooks.txt\n+++ /dev/null\n@@ -1,285 +0,0 @@\n-Hooks used by git\n-=================\n-\n-Hooks are little scripts you can place in `$GIT_DIR/hooks`\n-directory to trigger action at certain points.  When\n-`git-init` is run, a handful example hooks are copied in the\n-`hooks` directory of the new repository, but by default they are\n-all disabled.  To enable a hook, make it executable with `chmod +x`.\n-\n-This document describes the currently defined hooks.\n-\n-applypatch-msg\n---------------\n-\n-This hook is invoked by `git-am` script.  It takes a single\n-parameter, the name of the file that holds the proposed commit\n-log message.  Exiting with non-zero status causes\n-`git-am` to abort before applying the patch.\n-\n-The hook is allowed to edit the message file in place, and can\n-be used to normalize the message into some project standard\n-format (if the project has one). It can also be used to refuse\n-the commit after inspecting the message file.\n-\n-The default 'applypatch-msg' hook, when enabled, runs the\n-'commit-msg' hook, if the latter is enabled.\n-\n-pre-applypatch\n---------------\n-\n-This hook is invoked by `git-am`.  It takes no parameter,\n-and is invoked after the patch is applied, but before a commit\n-is made.  Exiting with non-zero status causes the working tree\n-after application of the patch not committed.\n-\n-It can be used to inspect the current working tree and refuse to\n-make a commit if it does not pass certain test.\n-\n-The default 'pre-applypatch' hook, when enabled, runs the\n-'pre-commit' hook, if the latter is enabled.\n-\n-post-applypatch\n----------------\n-\n-This hook is invoked by `git-am`.  It takes no parameter,\n-and is invoked after the patch is applied and a commit is made.\n-\n-This hook is meant primarily for notification, and cannot affect\n-the outcome of `git-am`.\n-\n-pre-commit\n-----------\n-\n-This hook is invoked by `git-commit`, and can be bypassed\n-with `\\--no-verify` option.  It takes no parameter, and is\n-invoked before obtaining the proposed commit log message and\n-making a commit.  Exiting with non-zero status from this script\n-causes the `git-commit` to abort.\n-\n-The default 'pre-commit' hook, when enabled, catches introduction\n-of lines with trailing whitespaces and aborts the commit when\n-such a line is found.\n-\n-All the `git-commit` hooks are invoked with the environment\n-variable `GIT_EDITOR=:` if the command will not bring up an editor\n-to modify the commit message.\n-\n-prepare-commit-msg\n-------------------\n-\n-This hook is invoked by `git-commit` right after preparing the\n-default log message, and before the editor is started.\n-\n-It takes one to three parameters.  The first is the name of the file\n-that the commit log message.  The second is the source of the commit\n-message, and can be: `message` (if a `\\-m` or `\\-F` option was\n-given); `template` (if a `\\-t` option was given or the\n-configuration option `commit.template` is set); `merge` (if the\n-commit is a merge or a `.git/MERGE_MSG` file exists); `squash`\n-(if a `.git/SQUASH_MSG` file exists); or `commit`, followed by\n-a commit SHA1 (if a `\\-c`, `\\-C` or `\\--amend` option was given).\n-\n-If the exit status is non-zero, `git-commit` will abort.\n-\n-The purpose of the hook is to edit the message file in place, and\n-it is not suppressed by the `\\--no-verify` option.  A non-zero exit\n-means a failure of the hook and aborts the commit.  It should not\n-be used as replacement for pre-commit hook.\n-\n-The sample `prepare-commit-msg` hook that comes with git comments\n-out the `Conflicts:` part of a merge's commit message.\n-\n-commit-msg\n-----------\n-\n-This hook is invoked by `git-commit`, and can be bypassed\n-with `\\--no-verify` option.  It takes a single parameter, the\n-name of the file that holds the proposed commit log message.\n-Exiting with non-zero status causes the `git-commit` to\n-abort.\n-\n-The hook is allowed to edit the message file in place, and can\n-be used to normalize the message into some project standard\n-format (if the project has one). It can also be used to refuse\n-the commit after inspecting the message file.\n-\n-The default 'commit-msg' hook, when enabled, detects duplicate\n-\"Signed-off-by\" lines, and aborts the commit if one is found.\n-\n-post-commit\n------------\n-\n-This hook is invoked by `git-commit`.  It takes no\n-parameter, and is invoked after a commit is made.\n-\n-This hook is meant primarily for notification, and cannot affect\n-the outcome of `git-commit`.\n-\n-post-checkout\n------------\n-\n-This hook is invoked when a `git-checkout` is run after having updated the\n-worktree.  The hook is given three parameters: the ref of the previous HEAD,\n-the ref of the new HEAD (which may or may not have changed), and a flag\n-indicating whether the checkout was a branch checkout (changing branches,\n-flag=1) or a file checkout (retrieving a file from the index, flag=0).\n-This hook cannot affect the outcome of `git-checkout`.\n-\n-This hook can be used to perform repository validity checks, auto-display\n-differences from the previous HEAD if different, or set working dir metadata\n-properties.\n-\n-post-merge\n------------\n-\n-This hook is invoked by `git-merge`, which happens when a `git pull`\n-is done on a local repository.  The hook takes a single parameter, a status\n-flag specifying whether or not the merge being done was a squash merge.\n-This hook cannot affect the outcome of `git-merge`.\n-\n-This hook can be used in conjunction with a corresponding pre-commit hook to\n-save and restore any form of metadata associated with the working tree\n-(eg: permissions/ownership, ACLS, etc).  See contrib/hooks/setgitperms.perl\n-for an example of how to do this.\n-\n-[[pre-receive]]\n-pre-receive\n------------\n-\n-This hook is invoked by `git-receive-pack` on the remote repository,\n-which happens when a `git push` is done on a local repository.\n-Just before starting to update refs on the remote repository, the\n-pre-receive hook is invoked.  Its exit status determines the success\n-or failure of the update.\n-\n-This hook executes once for the receive operation. It takes no\n-arguments, but for each ref to be updated it receives on standard\n-input a line of the format:\n-\n-  <old-value> SP <new-value> SP <ref-name> LF\n-\n-where `<old-value>` is the old object name stored in the ref,\n-`<new-value>` is the new object name to be stored in the ref and\n-`<ref-name>` is the full name of the ref.\n-When creating a new ref, `<old-value>` is 40 `0`.\n-\n-If the hook exits with non-zero status, none of the refs will be\n-updated. If the hook exits with zero, updating of individual refs can\n-still be prevented by the <<update,'update'>> hook.\n-\n-Both standard output and standard error output are forwarded to\n-`git-send-pack` on the other end, so you can simply `echo` messages\n-for the user.\n-\n-[[update]]\n-update\n-------\n-\n-This hook is invoked by `git-receive-pack` on the remote repository,\n-which happens when a `git push` is done on a local repository.\n-Just before updating the ref on the remote repository, the update hook\n-is invoked.  Its exit status determines the success or failure of\n-the ref update.\n-\n-The hook executes once for each ref to be updated, and takes\n-three parameters:\n-\n- - the name of the ref being updated,\n- - the old object name stored in the ref,\n- - and the new objectname to be stored in the ref.\n-\n-A zero exit from the update hook allows the ref to be updated.\n-Exiting with a non-zero status prevents `git-receive-pack`\n-from updating that ref.\n-\n-This hook can be used to prevent 'forced' update on certain refs by\n-making sure that the object name is a commit object that is a\n-descendant of the commit object named by the old object name.\n-That is, to enforce a \"fast forward only\" policy.\n-\n-It could also be used to log the old..new status.  However, it\n-does not know the entire set of branches, so it would end up\n-firing one e-mail per ref when used naively, though.  The\n-<<post-receive,'post-receive'>> hook is more suited to that.\n-\n-Another use suggested on the mailing list is to use this hook to\n-implement access control which is finer grained than the one\n-based on filesystem group.\n-\n-Both standard output and standard error output are forwarded to\n-`git-send-pack` on the other end, so you can simply `echo` messages\n-for the user.\n-\n-The default 'update' hook, when enabled--and with\n-`hooks.allowunannotated` config option turned on--prevents\n-unannotated tags to be pushed.\n-\n-[[post-receive]]\n-post-receive\n-------------\n-\n-This hook is invoked by `git-receive-pack` on the remote repository,\n-which happens when a `git push` is done on a local repository.\n-It executes on the remote repository once after all the refs have\n-been updated.\n-\n-This hook executes once for the receive operation.  It takes no\n-arguments, but gets the same information as the\n-<<pre-receive,'pre-receive'>>\n-hook does on its standard input.\n-\n-This hook does not affect the outcome of `git-receive-pack`, as it\n-is called after the real work is done.\n-\n-This supersedes the <<post-update,'post-update'>> hook in that it gets\n-both old and new values of all the refs in addition to their\n-names.\n-\n-Both standard output and standard error output are forwarded to\n-`git-send-pack` on the other end, so you can simply `echo` messages\n-for the user.\n-\n-The default 'post-receive' hook is empty, but there is\n-a sample script `post-receive-email` provided in the `contrib/hooks`\n-directory in git distribution, which implements sending commit\n-emails.\n-\n-[[post-update]]\n-post-update\n------------\n-\n-This hook is invoked by `git-receive-pack` on the remote repository,\n-which happens when a `git push` is done on a local repository.\n-It executes on the remote repository once after all the refs have\n-been updated.\n-\n-It takes a variable number of parameters, each of which is the\n-name of ref that was actually updated.\n-\n-This hook is meant primarily for notification, and cannot affect\n-the outcome of `git-receive-pack`.\n-\n-The 'post-update' hook can tell what are the heads that were pushed,\n-but it does not know what their original and updated values are,\n-so it is a poor place to do log old..new. The\n-<<post-receive,'post-receive'>> hook does get both original and\n-updated values of the refs. You might consider it instead if you need\n-them.\n-\n-When enabled, the default 'post-update' hook runs\n-`git-update-server-info` to keep the information used by dumb\n-transports (e.g., HTTP) up-to-date.  If you are publishing\n-a git repository that is accessible via HTTP, you should\n-probably enable this hook.\n-\n-Both standard output and standard error output are forwarded to\n-`git-send-pack` on the other end, so you can simply `echo` messages\n-for the user.\n-\n-pre-auto-gc\n------------\n-\n-This hook is invoked by `git-gc --auto`. It takes no parameter, and\n-exiting with non-zero status from this script causes the `git-gc --auto`\n-to abort.\n-- \n1.5.5.1.100.gc23d\n"},{"id":"75666","messageId":"fv9hlt$nvv$1@ger.gmane.org","threadId":"13329","inReplyTo":"20080430080820.ef5a4c2a.chriscool@tuxfamily.org","subject":"Re: [PATCH] Documentation: rename \"hooks.txt\" to \"githooks.txt\" and make it a man page","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2008-04-30T10:29:17Z","receivedAt":"2008-04-30T10:29:17Z","isPatch":true,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"[Cc: Christian Couder <chriscool@tuxfamily.org>, git@vger.kernel.org]\n\nChristian Couder wrote:\n\n> Also now \"gitcli(5)\" becomes \"gitcli(7)\".\n\n>  Documentation/githooks.txt |  301 ++++++++++++++++++++++++++++++++++++++++++++\n>  Documentation/hooks.txt    |  285 -----------------------------------------\n>  4 files changed, 304 insertions(+), 289 deletions(-)\n>  create mode 100644 Documentation/githooks.txt\n>  delete mode 100644 Documentation/hooks.txt\n\nPlease generate such rename patches with '-M' option, i.e. with rename\ndetection enabled.  This way patches are smaller, and it is easier to\nsee what has changed (beside renaming).\n\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"},{"id":"75714","messageId":"87ej8ngvdc.fsf@anzu.internal.golden-gryphon.com","threadId":"13329","inReplyTo":"20080430080820.ef5a4c2a.chriscool@tuxfamily.org","subject":"Re: [PATCH] Documentation: rename \"hooks.txt\" to \"githooks.txt\" and make it a man page","fromName":"Manoj Srivastava","fromEmail":"srivasta@ieee.org","sentAt":"2008-04-30T16:28:31Z","receivedAt":"2008-04-30T16:28:31Z","isPatch":true,"sender":{"key":"srivasta@ieee.org","avatar":null},"body":"Hi,\n\n        The documentation patch says:\n--- /dev/null\n+++ b/Documentation/githooks.txt\n@@ -0,0 +1,301 @@\n [snip]\n+pre-applypatch\n+--------------\n+\n+This hook is invoked by `git-am`.  It takes no parameter,\n+and is invoked after the patch is applied, but before a commit\n+is made.  Exiting with non-zero status causes the working tree\n+after application of the patch not committed.\n\n        I am afraid I can't parse the final sentence: I assume it means\n that the patched working tree is not committed, but the missing verb\n makes it harder for non-native speakers of the english language to\n understand what is meant here.\n\n        manoj\n-- \nBacked up the system lately?\nManoj Srivastava <srivasta@acm.org> <http://www.golden-gryphon.com/>  \n1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C\n"}]}