From d5784139def7af962c513f39bbef7fd72db02638 Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Wed, 20 Sep 2006 21:29:27 +0000 Subject: [PATCH] Autogenerated HTML docs for v1.4.2.1-g62e27 --- gitk.html | 19 +++++++++++++- gitk.txt | 9 +++++++ hooks.html | 73 ++++++++++++++++++++++++++++++++---------------------- hooks.txt | 56 ++++++++++++++++++++--------------------- 4 files changed, 98 insertions(+), 59 deletions(-) diff --git a/gitk.html b/gitk.html index 9d79ee949..2b32c8c50 100644 --- a/gitk.html +++ b/gitk.html @@ -314,6 +314,14 @@ frequently used options.

+--all +
+
+

+ Show all branches. +

+
+
<revs>
@@ -358,6 +366,15 @@ gitk --since="2 weeks ago" -- gitk gitk

+
+gitk --max-count=100 --all — Makefile +
+
+

+ Show at most 100 changes made to the file Makefile. Instead of only + looking for changes in the current branch look in all branches. +

+

See Also

@@ -406,7 +423,7 @@ gitk --since="2 weeks ago" -- gitk diff --git a/gitk.txt b/gitk.txt index 23be0050b..f1aeb07f6 100644 --- a/gitk.txt +++ b/gitk.txt @@ -37,6 +37,10 @@ frequently used options. Show commits older than a specific date. +--all:: + + Show all branches. + :: Limit the revisions to show. This can be either a single revision @@ -63,6 +67,11 @@ gitk --since="2 weeks ago" \-- gitk:: The "--" is necessary to avoid confusion with the *branch* named 'gitk' +gitk --max-count=100 --all -- Makefile:: + + Show at most 100 changes made to the file 'Makefile'. Instead of only + looking for changes in the current branch look in all branches. + See Also -------- 'qgit(1)':: diff --git a/hooks.html b/hooks.html index 9dec9bb37..0bd6d2f8e 100644 --- a/hooks.html +++ b/hooks.html @@ -267,8 +267,7 @@ div.exampleblock-content { directory to trigger action at certain points. When git-init-db is run, a handful example hooks are copied in the hooks directory of the new repository, but by default they are -all disabled. To enable a hook, make it executable with `chmod

-

+x`.

+all disabled. To enable a hook, make it executable with chmod +x.

This document describes the currently defined hooks.

@@ -277,14 +276,14 @@ all disabled. To enable a hook, make it executable with `chmod

This hook is invoked by git-applypatch script, which is typically invoked by git-applymbox. It takes a single parameter, the name of the file that holds the proposed commit -log message. Exiting with non-zero status causes the -git-applypatch to abort before applying the patch.

+log message. Exiting with non-zero status causes +git-applypatch to abort before applying the patch.

The hook is allowed to edit the message file in place, and can be used to normalize the message into some project standard format (if the project has one). It can also be used to refuse the commit after inspecting the message file.

-

The default applypatch-msg hook, when enabled, runs the -commit-msg hook, if the latter is enabled.

+

The default applypatch-msg hook, when enabled, runs the +commit-msg hook, if the latter is enabled.

pre-applypatch

@@ -295,8 +294,8 @@ is made. Exiting with non-zero status causes the working tree after application of the patch not committed.

It can be used to inspect the current working tree and refuse to make a commit if it does not pass certain test.

-

The default pre-applypatch hook, when enabled, runs the -pre-commit hook, if the latter is enabled.

+

The default pre-applypatch hook, when enabled, runs the +pre-commit hook, if the latter is enabled.

post-applypatch

@@ -313,9 +312,9 @@ with --no-verify option. It takes no parameter, and is invoked before obtaining the proposed commit log message and making a commit. Exiting with non-zero status from this script causes the git-commit to abort.

-

The default pre-commit hook, when enabled, catches introduction +

The default pre-commit hook, when enabled, catches introduction of lines with trailing whitespaces and aborts the commit when -a such line is found.

+such a line is found.

commit-msg

@@ -328,8 +327,8 @@ abort.

be used to normalize the message into some project standard format (if the project has one). It can also be used to refuse the commit after inspecting the message file.

-

The default commit-msg hook, when enabled, detects duplicate -Signed-off-by: lines, and aborts the commit when one is found.

+

The default commit-msg hook, when enabled, detects duplicate +"Signed-off-by" lines, and aborts the commit if one is found.

post-commit

@@ -337,21 +336,35 @@ Signed-off-by: lines, and aborts the commit when one is found.

parameter, and is invoked after a commit is made.

This hook is meant primarily for notification, and cannot affect the outcome of git-commit.

-

The default post-commit hook, when enabled, demonstrates how to +

The default post-commit hook, when enabled, demonstrates how to send out a commit notification e-mail.

update

This hook is invoked by git-receive-pack on the remote repository, -which is happens when a git push is done on a local repository. +which happens when a git push is done on a local repository. Just before updating the ref on the remote repository, the update hook is invoked. Its exit status determines the success or failure of the ref update.

The hook executes once for each ref to be updated, and takes -three parameters: - - the name of the ref being updated, - - the old object name stored in the ref, - - and the new objectname to be stored in the ref.

+three parameters:

+
    +
  • +

    +the name of the ref being updated, +

    +
    • +
  • +

    +the old object name stored in the ref, +

    +
    • +
  • +

    +and the new objectname to be stored in the ref. +

    +
    • +

A zero exit from the update hook allows the ref to be updated. Exiting with a non-zero status prevents git-receive-pack from updating the ref.

@@ -365,35 +378,35 @@ firing one e-mail per ref when used naively, though.

Another use suggested on the mailing list is to use this hook to implement access control which is finer grained than the one based on filesystem group.

-

The standard output of this hook is sent to /dev/null; if you -want to report something to the git-send-pack on the other end, -you can redirect your output to your stderr.

+

The standard output of this hook is sent to /dev/null; if you +want to report something to the git-send-pack on the other end, +you can redirect your output to your stderr.

post-update

This hook is invoked by git-receive-pack on the remote repository, -which is happens when a git push is done on a local repository. +which happens when a git push is done on a local repository. It executes on the remote repository once after all the refs have been updated.

It takes a variable number of parameters, each of which is the name of ref that was actually updated.

This hook is meant primarily for notification, and cannot affect the outcome of git-receive-pack.

-

The post-update hook can tell what are the heads that were pushed, +

The post-update hook can tell what are the heads that were pushed, but it does not know what their original and updated values are, so it is a poor place to do log old..new.

-

The default post-update hook, when enabled, runs +

When enabled, the default post-update hook runs git-update-server-info to keep the information used by dumb -transports (e.g., http) up-to-date. If you are publishing -a git repository that is accessible via http, you should +transports (e.g., HTTP) up-to-date. If you are publishing +a git repository that is accessible via HTTP, you should probably enable this hook.

-

The standard output of this hook is sent to /dev/null; if you -want to report something to the git-send-pack on the other end, -you can redirect your output to your stderr.

+

The standard output of this hook is sent to /dev/null; if you +want to report something to the git-send-pack on the other end, +you can redirect your output to your stderr.

diff --git a/hooks.txt b/hooks.txt index 898b4aaf8..517f49b5c 100644 --- a/hooks.txt +++ b/hooks.txt @@ -5,8 +5,7 @@ Hooks are little scripts you can place in `$GIT_DIR/hooks` directory to trigger action at certain points. When `git-init-db` is run, a handful example hooks are copied in the `hooks` directory of the new repository, but by default they are -all disabled. To enable a hook, make it executable with `chmod -+x`. +all disabled. To enable a hook, make it executable with `chmod +x`. This document describes the currently defined hooks. @@ -16,16 +15,16 @@ applypatch-msg This hook is invoked by `git-applypatch` script, which is typically invoked by `git-applymbox`. It takes a single parameter, the name of the file that holds the proposed commit -log message. Exiting with non-zero status causes the -'git-applypatch' to abort before applying the patch. +log message. Exiting with non-zero status causes +`git-applypatch` to abort before applying the patch. The hook is allowed to edit the message file in place, and can be used to normalize the message into some project standard format (if the project has one). It can also be used to refuse the commit after inspecting the message file. -The default applypatch-msg hook, when enabled, runs the -commit-msg hook, if the latter is enabled. +The default 'applypatch-msg' hook, when enabled, runs the +'commit-msg' hook, if the latter is enabled. pre-applypatch -------------- @@ -39,8 +38,8 @@ after application of the patch not committed. It can be used to inspect the current working tree and refuse to make a commit if it does not pass certain test. -The default pre-applypatch hook, when enabled, runs the -pre-commit hook, if the latter is enabled. +The default 'pre-applypatch' hook, when enabled, runs the +'pre-commit' hook, if the latter is enabled. post-applypatch --------------- @@ -61,9 +60,9 @@ invoked before obtaining the proposed commit log message and making a commit. Exiting with non-zero status from this script causes the `git-commit` to abort. -The default pre-commit hook, when enabled, catches introduction +The default 'pre-commit' hook, when enabled, catches introduction of lines with trailing whitespaces and aborts the commit when -a such line is found. +such a line is found. commit-msg ---------- @@ -79,8 +78,8 @@ be used to normalize the message into some project standard format (if the project has one). It can also be used to refuse the commit after inspecting the message file. -The default commit-msg hook, when enabled, detects duplicate -Signed-off-by: lines, and aborts the commit when one is found. +The default 'commit-msg' hook, when enabled, detects duplicate +"Signed-off-by" lines, and aborts the commit if one is found. post-commit ----------- @@ -91,23 +90,24 @@ parameter, and is invoked after a commit is made. This hook is meant primarily for notification, and cannot affect the outcome of `git-commit`. -The default post-commit hook, when enabled, demonstrates how to +The default 'post-commit' hook, when enabled, demonstrates how to send out a commit notification e-mail. update ------ This hook is invoked by `git-receive-pack` on the remote repository, -which is happens when a `git push` is done on a local repository. +which happens when a `git push` is done on a local repository. Just before updating the ref on the remote repository, the update hook is invoked. Its exit status determines the success or failure of the ref update. The hook executes once for each ref to be updated, and takes three parameters: - - the name of the ref being updated, - - the old object name stored in the ref, - - and the new objectname to be stored in the ref. + + - the name of the ref being updated, + - the old object name stored in the ref, + - and the new objectname to be stored in the ref. A zero exit from the update hook allows the ref to be updated. Exiting with a non-zero status prevents `git-receive-pack` @@ -126,16 +126,16 @@ Another use suggested on the mailing list is to use this hook to implement access control which is finer grained than the one based on filesystem group. -The standard output of this hook is sent to /dev/null; if you -want to report something to the git-send-pack on the other end, -you can redirect your output to your stderr. +The standard output of this hook is sent to `/dev/null`; if you +want to report something to the `git-send-pack` on the other end, +you can redirect your output to your `stderr`. post-update ----------- This hook is invoked by `git-receive-pack` on the remote repository, -which is happens when a `git push` is done on a local repository. +which happens when a `git push` is done on a local repository. It executes on the remote repository once after all the refs have been updated. @@ -145,16 +145,16 @@ name of ref that was actually updated. This hook is meant primarily for notification, and cannot affect the outcome of `git-receive-pack`. -The post-update hook can tell what are the heads that were pushed, +The 'post-update' hook can tell what are the heads that were pushed, but it does not know what their original and updated values are, so it is a poor place to do log old..new. -The default post-update hook, when enabled, runs +When enabled, the default 'post-update' hook runs `git-update-server-info` to keep the information used by dumb -transports (e.g., http) up-to-date. If you are publishing -a git repository that is accessible via http, you should +transports (e.g., HTTP) up-to-date. If you are publishing +a git repository that is accessible via HTTP, you should probably enable this hook. -The standard output of this hook is sent to /dev/null; if you -want to report something to the git-send-pack on the other end, -you can redirect your output to your stderr. +The standard output of this hook is sent to `/dev/null`; if you +want to report something to the `git-send-pack` on the other end, +you can redirect your output to your `stderr`. -- 2.26.2