[PATCH v2] Documentation/githooks: Explain pre-rebase parameters
From: W. Trevor King <hidden>
Date: 2016-06-15 22:56:14
Subsystem:
documentation, the rest · Maintainers:
Jonathan Corbet, Linus Torvalds
Possibly related (same subject, not in this thread)
- 2016-06-15 · Re: [PATCH v2] Documentation/githooks: Explain pre-rebase parameters · Junio C Hamano <hidden>
- 2016-06-15 · Re: [PATCH v2] Documentation/githooks: Explain pre-rebase parameters · W. Trevor King <hidden>
- 2016-06-15 · Re: [PATCH v2] Documentation/githooks: Explain pre-rebase parameters · Junio C Hamano <hidden>
From: "W. Trevor King" <redacted> Descriptions borrowed from templates/hooks--pre-rebase.sample. Signed-off-by: W. Trevor King <redacted> --- Changes from v1: * Replaced "empty" with "missing" for second parameter. Documentation/githooks.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/githooks.txt b/Documentation/githooks.txt
index b9003fe..dfd5959 100644
--- a/Documentation/githooks.txt
+++ b/Documentation/githooks.txt@@ -140,9 +140,10 @@ the outcome of 'git commit'. pre-rebase ~~~~~~~~~~ -This hook is called by 'git rebase' and can be used to prevent a branch -from getting rebased. - +This hook is called by 'git rebase' and can be used to prevent a +branch from getting rebased. The hook takes two parameters: the +upstream the series was forked from and the branch being rebased. The +second parameter will be missing when rebasing the current branch. post-checkout ~~~~~~~~~~~~~
--
1.8.2.rc0.16.g20a599e