{
    "mode": "man",
    "parameter": "githooks",
    "section": "5",
    "url": "https://www.chedong.com/phpMan.php/man/githooks/5/json",
    "generated": "2026-06-15T16:02:00Z",
    "synopsis": "$GITDIR/hooks/* (or `git config core.hooksPath`/*)",
    "sections": {
        "NAME": {
            "content": "githooks - Hooks used by Git\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "$GITDIR/hooks/* (or `git config core.hooksPath`/*)\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "Hooks are programs you can place in a hooks directory to trigger actions at certain points in\ngit’s execution. Hooks that don’t have the executable bit set are ignored.\n\nBy default the hooks directory is $GITDIR/hooks, but that can be changed via the\ncore.hooksPath configuration variable (see git-config(1)).\n\nBefore Git invokes a hook, it changes its working directory to either $GITDIR in a bare\nrepository or the root of the working tree in a non-bare repository. An exception are hooks\ntriggered during a push (pre-receive, update, post-receive, post-update, push-to-checkout)\nwhich are always executed in $GITDIR.\n\nHooks can get their arguments via the environment, command-line arguments, and stdin. See the\ndocumentation for each hook below for details.\n\ngit init may copy hooks to the new repository, depending on its configuration. See the\n\"TEMPLATE DIRECTORY\" section in git-init(1) for details. When the rest of this document\nrefers to \"default hooks\" it’s talking about the default template shipped with Git.\n\nThe currently supported hooks are described below.\n",
            "subsections": []
        },
        "HOOKS": {
            "content": "",
            "subsections": [
                {
                    "name": "applypatch-msg",
                    "content": "This hook is invoked by git-am(1). It takes a single parameter, the name of the file that\nholds the proposed commit log message. Exiting with a non-zero status causes git am to abort\nbefore applying the patch.\n\nThe hook is allowed to edit the message file in place, and can be used to normalize the\nmessage into some project standard format. It can also be used to refuse the commit after\ninspecting the message file.\n\nThe default applypatch-msg hook, when enabled, runs the commit-msg hook, if the latter is\nenabled.\n"
                },
                {
                    "name": "pre-applypatch",
                    "content": "This hook is invoked by git-am(1). It takes no parameter, and is invoked after the patch is\napplied, but before a commit is made.\n\nIf it exits with non-zero status, then the working tree will not be committed after applying\nthe patch.\n\nIt can be used to inspect the current working tree and refuse to make a commit if it does not\npass certain test.\n\nThe default pre-applypatch hook, when enabled, runs the pre-commit hook, if the latter is\nenabled.\n"
                },
                {
                    "name": "post-applypatch",
                    "content": "This hook is invoked by git-am(1). It takes no parameter, and is invoked after the patch is\napplied and a commit is made.\n\nThis hook is meant primarily for notification, and cannot affect the outcome of git am.\n"
                },
                {
                    "name": "pre-commit",
                    "content": "This hook is invoked by git-commit(1), and can be bypassed with the --no-verify option. It\ntakes no parameters, and is invoked before obtaining the proposed commit log message and\nmaking a commit. Exiting with a non-zero status from this script causes the git commit\ncommand to abort before creating a commit.\n\nThe default pre-commit hook, when enabled, catches introduction of lines with trailing\nwhitespaces and aborts the commit when such a line is found.\n\nAll the git commit hooks are invoked with the environment variable GITEDITOR=: if the\ncommand will not bring up an editor to modify the commit message.\n\nThe default pre-commit hook, when enabled—and with the hooks.allownonascii config option\nunset or set to false—prevents the use of non-ASCII filenames.\n"
                },
                {
                    "name": "pre-merge-commit",
                    "content": "This hook is invoked by git-merge(1), and can be bypassed with the --no-verify option. It\ntakes no parameters, and is invoked after the merge has been carried out successfully and\nbefore obtaining the proposed commit log message to make a commit. Exiting with a non-zero\nstatus from this script causes the git merge command to abort before creating a commit.\n\nThe default pre-merge-commit hook, when enabled, runs the pre-commit hook, if the latter is\nenabled.\n\nThis hook is invoked with the environment variable GITEDITOR=: if the command will not bring\nup an editor to modify the commit message.\n\nIf the merge cannot be carried out automatically, the conflicts need to be resolved and the\nresult committed separately (see git-merge(1)). At that point, this hook will not be\nexecuted, but the pre-commit hook will, if it is enabled.\n"
                },
                {
                    "name": "prepare-commit-msg",
                    "content": "This hook is invoked by git-commit(1) right after preparing the default log message, and\nbefore the editor is started.\n\nIt takes one to three parameters. The first is the name of the file that contains the commit\nlog message. The second is the source of the commit message, and can be: message (if a -m or"
                },
                {
                    "name": "-F -t",
                    "content": "commit.template is set); merge (if the commit is a merge or a .git/MERGEMSG file exists);\nsquash (if a .git/SQUASHMSG file exists); or commit, followed by a commit object name (if a",
                    "flag": "-t"
                },
                {
                    "name": "-c -C --amend",
                    "content": "If the exit status is non-zero, git commit will abort.\n\nThe purpose of the hook is to edit the message file in place, and it is not suppressed by the\n--no-verify option. A non-zero exit means a failure of the hook and aborts the commit. It\nshould not be used as replacement for pre-commit hook.\n\nThe sample prepare-commit-msg hook that comes with Git removes the help message found in the\ncommented portion of the commit template.\n",
                    "flag": "-C",
                    "long": "--amend"
                },
                {
                    "name": "commit-msg",
                    "content": "This hook is invoked by git-commit(1) and git-merge(1), and can be bypassed with the\n--no-verify option. It takes a single parameter, the name of the file that holds the proposed\ncommit log message. Exiting with a non-zero status causes the command to abort.\n\nThe hook is allowed to edit the message file in place, and can be used to normalize the\nmessage into some project standard format. It can also be used to refuse the commit after\ninspecting the message file.\n\nThe default commit-msg hook, when enabled, detects duplicate Signed-off-by trailers, and\naborts the commit if one is found.\n"
                },
                {
                    "name": "post-commit",
                    "content": "This hook is invoked by git-commit(1). It takes no parameters, and is invoked after a commit\nis made.\n\nThis hook is meant primarily for notification, and cannot affect the outcome of git commit.\n"
                },
                {
                    "name": "pre-rebase",
                    "content": "This hook is called by git-rebase(1) and can be used to prevent a branch from getting\nrebased. The hook may be called with one or two parameters. The first parameter is the\nupstream from which the series was forked. The second parameter is the branch being rebased,\nand is not set when rebasing the current branch.\n"
                },
                {
                    "name": "post-checkout",
                    "content": "This hook is invoked when a git-checkout(1) or git-switch(1) is run after having updated the\nworktree. The hook is given three parameters: the ref of the previous HEAD, the ref of the\nnew HEAD (which may or may not have changed), and a flag indicating whether the checkout was\na branch checkout (changing branches, flag=1) or a file checkout (retrieving a file from the\nindex, flag=0). This hook cannot affect the outcome of git switch or git checkout, other than\nthat the hook’s exit status becomes the exit status of these two commands.\n\nIt is also run after git-clone(1), unless the --no-checkout (-n) option is used. The first\nparameter given to the hook is the null-ref, the second the ref of the new HEAD and the flag\nis always 1. Likewise for git worktree add unless --no-checkout is used.\n\nThis hook can be used to perform repository validity checks, auto-display differences from\nthe previous HEAD if different, or set working dir metadata properties.\n"
                },
                {
                    "name": "post-merge",
                    "content": "This hook is invoked by git-merge(1), which happens when a git pull is done on a local\nrepository. The hook takes a single parameter, a status flag specifying whether or not the\nmerge being done was a squash merge. This hook cannot affect the outcome of git merge and is\nnot executed, if the merge failed due to conflicts.\n\nThis hook can be used in conjunction with a corresponding pre-commit hook to save and restore\nany form of metadata associated with the working tree (e.g.: permissions/ownership, ACLS,\netc). See contrib/hooks/setgitperms.perl for an example of how to do this.\n"
                },
                {
                    "name": "pre-push",
                    "content": "This hook is called by git-push(1) and can be used to prevent a push from taking place. The\nhook is called with two parameters which provide the name and location of the destination\nremote, if a named remote is not being used both values will be the same.\n\nInformation about what is to be pushed is provided on the hook’s standard input with lines of\nthe form:\n\n<local ref> SP <local object name> SP <remote ref> SP <remote object name> LF\n\nFor instance, if the command git push origin master:foreign were run the hook would receive a\nline like the following:\n\nrefs/heads/master 67890 refs/heads/foreign 12345\n\nalthough the full object name would be supplied. If the foreign ref does not yet exist the\n<remote object name> will be the all-zeroes object name. If a ref is to be deleted, the\n<local ref> will be supplied as (delete) and the <local object name> will be the all-zeroes\nobject name. If the local commit was specified by something other than a name which could be\nexpanded (such as HEAD~, or an object name) it will be supplied as it was originally given.\n\nIf this hook exits with a non-zero status, git push will abort without pushing anything.\nInformation about why the push is rejected may be sent to the user by writing to standard\nerror.\n"
                },
                {
                    "name": "pre-receive",
                    "content": "This hook is invoked by git-receive-pack(1) when it reacts to git push and updates\nreference(s) in its repository. Just before starting to update refs on the remote repository,\nthe pre-receive hook is invoked. Its exit status determines the success or failure of the\nupdate.\n\nThis hook executes once for the receive operation. It takes no arguments, but for each ref to\nbe updated it receives on standard input a line of the format:\n\n<old-value> SP <new-value> SP <ref-name> LF\n\nwhere <old-value> is the old object name stored in the ref, <new-value> is the new object\nname to be stored in the ref and <ref-name> is the full name of the ref. When creating a new\nref, <old-value> is the all-zeroes object name.\n\nIf the hook exits with non-zero status, none of the refs will be updated. If the hook exits\nwith zero, updating of individual refs can still be prevented by the update hook.\n\nBoth standard output and standard error output are forwarded to git send-pack on the other\nend, so you can simply echo messages for the user.\n\nThe number of push options given on the command line of git push --push-option=... can be\nread from the environment variable GITPUSHOPTIONCOUNT, and the options themselves are\nfound in GITPUSHOPTION0, GITPUSHOPTION1,... If it is negotiated to not use the push\noptions phase, the environment variables will not be set. If the client selects to use push\noptions, but doesn’t transmit any, the count variable will be set to zero,\nGITPUSHOPTIONCOUNT=0.\n\nSee the section on \"Quarantine Environment\" in git-receive-pack(1) for some caveats.\n"
                },
                {
                    "name": "update",
                    "content": "This hook is invoked by git-receive-pack(1) when it reacts to git push and updates\nreference(s) in its repository. Just before updating the ref on the remote repository, the\nupdate hook is invoked. Its exit status determines the success or failure of the ref update.\n\nThe hook executes once for each ref to be updated, and takes three parameters:\n\n•   the name of the ref being updated,\n\n•   the old object name stored in the ref,\n\n•   and the new object name to be stored in the ref.\n\nA zero exit from the update hook allows the ref to be updated. Exiting with a non-zero status\nprevents git receive-pack from updating that ref.\n\nThis hook can be used to prevent forced update on certain refs by making sure that the object\nname is a commit object that is a descendant of the commit object named by the old object\nname. That is, to enforce a \"fast-forward only\" policy.\n\nIt could also be used to log the old..new status. However, it does not know the entire set of\nbranches, so it would end up firing one e-mail per ref when used naively, though. The\npost-receive hook is more suited to that.\n\nIn an environment that restricts the users' access only to git commands over the wire, this\nhook can be used to implement access control without relying on filesystem ownership and\ngroup membership. See git-shell(1) for how you might use the login shell to restrict the\nuser’s access to only git commands.\n\nBoth standard output and standard error output are forwarded to git send-pack on the other\nend, so you can simply echo messages for the user.\n\nThe default update hook, when enabled—and with hooks.allowunannotated config option unset or\nset to false—prevents unannotated tags to be pushed.\n"
                },
                {
                    "name": "proc-receive",
                    "content": "This hook is invoked by git-receive-pack(1). If the server has set the multi-valued config\nvariable receive.procReceiveRefs, and the commands sent to receive-pack have matching\nreference names, these commands will be executed by this hook, instead of by the internal\nexecutecommands() function. This hook is responsible for updating the relevant references\nand reporting the results back to receive-pack.\n\nThis hook executes once for the receive operation. It takes no arguments, but uses a pkt-line\nformat protocol to communicate with receive-pack to read commands, push-options and send\nresults. In the following example for the protocol, the letter S stands for receive-pack and\nthe letter H stands for this hook.\n\n# Version and features negotiation.\nS: PKT-LINE(version=1\\0push-options atomic...)\nS: flush-pkt\nH: PKT-LINE(version=1\\0push-options...)\nH: flush-pkt\n\n# Send commands from server to the hook.\nS: PKT-LINE(<old-oid> <new-oid> <ref>)\nS: ... ...\nS: flush-pkt\n# Send push-options only if the 'push-options' feature is enabled.\nS: PKT-LINE(push-option)\nS: ... ...\nS: flush-pkt\n\n# Receive result from the hook.\n# OK, run this command successfully.\nH: PKT-LINE(ok <ref>)\n# NO, I reject it.\nH: PKT-LINE(ng <ref> <reason>)\n# Fall through, let 'receive-pack' to execute it.\nH: PKT-LINE(ok <ref>)\nH: PKT-LINE(option fall-through)\n# OK, but has an alternate reference.  The alternate reference name\n# and other status can be given in option directives.\nH: PKT-LINE(ok <ref>)\nH: PKT-LINE(option refname <refname>)\nH: PKT-LINE(option old-oid <old-oid>)\nH: PKT-LINE(option new-oid <new-oid>)\nH: PKT-LINE(option forced-update)\nH: ... ...\nH: flush-pkt\n\nEach command for the proc-receive hook may point to a pseudo-reference and always has a\nzero-old as its old-oid, while the proc-receive hook may update an alternate reference and\nthe alternate reference may exist already with a non-zero old-oid. For this case, this hook\nwill use \"option\" directives to report extended attributes for the reference given by the\nleading \"ok\" directive.\n\nThe report of the commands of this hook should have the same order as the input. The exit\nstatus of the proc-receive hook only determines the success or failure of the group of\ncommands sent to it, unless atomic push is in use.\n"
                },
                {
                    "name": "post-receive",
                    "content": "This hook is invoked by git-receive-pack(1) when it reacts to git push and updates\nreference(s) in its repository. It executes on the remote repository once after all the refs\nhave been updated.\n\nThis hook executes once for the receive operation. It takes no arguments, but gets the same\ninformation as the pre-receive hook does on its standard input.\n\nThis hook does not affect the outcome of git receive-pack, as it is called after the real\nwork is done.\n\nThis supersedes the post-update hook in that it gets both old and new values of all the refs\nin addition to their names.\n\nBoth standard output and standard error output are forwarded to git send-pack on the other\nend, so you can simply echo messages for the user.\n\nThe default post-receive hook is empty, but there is a sample script post-receive-email\nprovided in the contrib/hooks directory in Git distribution, which implements sending commit\nemails.\n\nThe number of push options given on the command line of git push --push-option=... can be\nread from the environment variable GITPUSHOPTIONCOUNT, and the options themselves are\nfound in GITPUSHOPTION0, GITPUSHOPTION1,... If it is negotiated to not use the push\noptions phase, the environment variables will not be set. If the client selects to use push\noptions, but doesn’t transmit any, the count variable will be set to zero,\nGITPUSHOPTIONCOUNT=0.\n"
                },
                {
                    "name": "post-update",
                    "content": "This hook is invoked by git-receive-pack(1) when it reacts to git push and updates\nreference(s) in its repository. It executes on the remote repository once after all the refs\nhave been updated.\n\nIt takes a variable number of parameters, each of which is the name of ref that was actually\nupdated.\n\nThis hook is meant primarily for notification, and cannot affect the outcome of git\nreceive-pack.\n\nThe post-update hook can tell what are the heads that were pushed, but it does not know what\ntheir original and updated values are, so it is a poor place to do log old..new. The\npost-receive hook does get both original and updated values of the refs. You might consider\nit instead if you need them.\n\nWhen enabled, the default post-update hook runs git update-server-info to keep the\ninformation used by dumb transports (e.g., HTTP) up to date. If you are publishing a Git\nrepository that is accessible via HTTP, you should probably enable this hook.\n\nBoth standard output and standard error output are forwarded to git send-pack on the other\nend, so you can simply echo messages for the user.\n"
                },
                {
                    "name": "reference-transaction",
                    "content": "This hook is invoked by any Git command that performs reference updates. It executes whenever\na reference transaction is prepared, committed or aborted and may thus get called multiple\ntimes. The hook does not cover symbolic references (but that may change in the future).\n\nThe hook takes exactly one argument, which is the current state the given reference\ntransaction is in:\n\n•   \"prepared\": All reference updates have been queued to the transaction and references were\nlocked on disk.\n\n•   \"committed\": The reference transaction was committed and all references now have their\nrespective new value.\n\n•   \"aborted\": The reference transaction was aborted, no changes were performed and the locks\nhave been released.\n\nFor each reference update that was added to the transaction, the hook receives on standard\ninput a line of the format:\n\n<old-value> SP <new-value> SP <ref-name> LF\n\nwhere <old-value> is the old object name passed into the reference transaction, <new-value>\nis the new object name to be stored in the ref and <ref-name> is the full name of the ref.\nWhen force updating the reference regardless of its current value or when the reference is to\nbe created anew, <old-value> is the all-zeroes object name. To distinguish these cases, you\ncan inspect the current value of <ref-name> via git rev-parse.\n\nThe exit status of the hook is ignored for any state except for the \"prepared\" state. In the\n\"prepared\" state, a non-zero exit status will cause the transaction to be aborted. The hook\nwill not be called with \"aborted\" state in that case.\n"
                },
                {
                    "name": "push-to-checkout",
                    "content": "This hook is invoked by git-receive-pack(1) when it reacts to git push and updates\nreference(s) in its repository, and when the push tries to update the branch that is\ncurrently checked out and the receive.denyCurrentBranch configuration variable is set to\nupdateInstead. Such a push by default is refused if the working tree and the index of the\nremote repository has any difference from the currently checked out commit; when both the\nworking tree and the index match the current commit, they are updated to match the newly\npushed tip of the branch. This hook is to be used to override the default behaviour.\n\nThe hook receives the commit with which the tip of the current branch is going to be updated.\nIt can exit with a non-zero status to refuse the push (when it does so, it must not modify\nthe index or the working tree). Or it can make any necessary changes to the working tree and\nto the index to bring them to the desired state when the tip of the current branch is updated\nto the new commit, and exit with a zero status.\n\nFor example, the hook can simply run git read-tree -u -m HEAD \"$1\" in order to emulate git\nfetch that is run in the reverse direction with git push, as the two-tree form of git\nread-tree -u -m is essentially the same as git switch or git checkout that switches branches\nwhile keeping the local changes in the working tree that do not interfere with the difference\nbetween the branches.\n"
                },
                {
                    "name": "pre-auto-gc",
                    "content": "This hook is invoked by git gc --auto (see git-gc(1)). It takes no parameter, and exiting\nwith non-zero status from this script causes the git gc --auto to abort.\n"
                },
                {
                    "name": "post-rewrite",
                    "content": "This hook is invoked by commands that rewrite commits (git-commit(1) when called with --amend\nand git-rebase(1); however, full-history (re)writing tools like git-fast-import(1) or\ngit-filter-repo[1] typically do not call it!). Its first argument denotes the command it was\ninvoked by: currently one of amend or rebase. Further command-dependent arguments may be\npassed in the future.\n\nThe hook receives a list of the rewritten commits on stdin, in the format\n\n<old-object-name> SP <new-object-name> [ SP <extra-info> ] LF\n\nThe extra-info is again command-dependent. If it is empty, the preceding SP is also omitted.\nCurrently, no commands pass any extra-info.\n\nThe hook always runs after the automatic note copying (see \"notes.rewrite.<command>\" in git-\nconfig(1)) has happened, and thus has access to these notes.\n\nThe following command-specific comments apply:\n\nrebase\nFor the squash and fixup operation, all commits that were squashed are listed as being\nrewritten to the squashed commit. This means that there will be several lines sharing the\nsame new-object-name.\n\nThe commits are guaranteed to be listed in the order that they were processed by rebase.\n"
                },
                {
                    "name": "sendemail-validate",
                    "content": "This hook is invoked by git-send-email(1). It takes a single parameter, the name of the file\nthat holds the e-mail to be sent. Exiting with a non-zero status causes git send-email to\nabort before sending any e-mails.\n"
                },
                {
                    "name": "fsmonitor-watchman",
                    "content": "This hook is invoked when the configuration option core.fsmonitor is set to\n.git/hooks/fsmonitor-watchman or .git/hooks/fsmonitor-watchmanv2 depending on the version of\nthe hook to use.\n\nVersion 1 takes two arguments, a version (1) and the time in elapsed nanoseconds since\nmidnight, January 1, 1970.\n\nVersion 2 takes two arguments, a version (2) and a token that is used for identifying changes\nsince the token. For watchman this would be a clock id. This version must output to stdout\nthe new token followed by a NUL before the list of files.\n\nThe hook should output to stdout the list of all files in the working directory that may have\nchanged since the requested time. The logic should be inclusive so that it does not miss any\npotential changes. The paths should be relative to the root of the working directory and be\nseparated by a single NUL.\n\nIt is OK to include files which have not actually changed. All changes including\nnewly-created and deleted files should be included. When files are renamed, both the old and\nthe new name should be included.\n\nGit will limit what files it checks for changes as well as which directories are checked for\nuntracked files based on the path names given.\n\nAn optimized way to tell git \"all files have changed\" is to return the filename /.\n\nThe exit status determines whether git will use the data from the hook to limit its search.\nOn error, it will fall back to verifying all files and folders.\n"
                },
                {
                    "name": "p4-changelist",
                    "content": "This hook is invoked by git-p4 submit.\n\nThe p4-changelist hook is executed after the changelist message has been edited by the user.\nIt can be bypassed with the --no-verify option. It takes a single parameter, the name of the\nfile that holds the proposed changelist text. Exiting with a non-zero status causes the\ncommand to abort.\n\nThe hook is allowed to edit the changelist file and can be used to normalize the text into\nsome project standard format. It can also be used to refuse the Submit after inspect the\nmessage file.\n\nRun git-p4 submit --help for details.\n"
                },
                {
                    "name": "p4-prepare-changelist",
                    "content": "This hook is invoked by git-p4 submit.\n\nThe p4-prepare-changelist hook is executed right after preparing the default changelist\nmessage and before the editor is started. It takes one parameter, the name of the file that\ncontains the changelist text. Exiting with a non-zero status from the script will abort the\nprocess.\n\nThe purpose of the hook is to edit the message file in place, and it is not suppressed by the\n--no-verify option. This hook is called even if --prepare-p4-only is set.\n\nRun git-p4 submit --help for details.\n"
                },
                {
                    "name": "p4-post-changelist",
                    "content": "This hook is invoked by git-p4 submit.\n\nThe p4-post-changelist hook is invoked after the submit has successfully occurred in P4. It\ntakes no parameters and is meant primarily for notification and cannot affect the outcome of\nthe git p4 submit action.\n\nRun git-p4 submit --help for details.\n"
                },
                {
                    "name": "p4-pre-submit",
                    "content": "This hook is invoked by git-p4 submit. It takes no parameters and nothing from standard\ninput. Exiting with non-zero status from this script prevent git-p4 submit from launching. It\ncan be bypassed with the --no-verify command line option. Run git-p4 submit --help for\ndetails.\n"
                },
                {
                    "name": "post-index-change",
                    "content": "This hook is invoked when the index is written in read-cache.c dowritelockedindex.\n\nThe first parameter passed to the hook is the indicator for the working directory being\nupdated. \"1\" meaning working directory was updated or \"0\" when the working directory was not\nupdated.\n\nThe second parameter passed to the hook is the indicator for whether or not the index was\nupdated and the skip-worktree bit could have changed. \"1\" meaning skip-worktree bits could\nhave been updated and \"0\" meaning they were not.\n\nOnly one parameter should be set to \"1\" when the hook runs. The hook running passing \"1\", \"1\"\nshould not be possible.\n"
                }
            ]
        },
        "GIT": {
            "content": "Part of the git(1) suite\n",
            "subsections": []
        },
        "NOTES": {
            "content": "1. git-filter-repo\nhttps://github.com/newren/git-filter-repo\n\n\n\nGit 2.34.1                                   02/26/2026                                  GITHOOKS(5)",
            "subsections": []
        }
    },
    "summary": "githooks - Hooks used by Git",
    "flags": [],
    "examples": [],
    "see_also": []
}