David Turner <dturner@xxxxxxxxxxxxxxxx> writes:
> Sorry about that -- the documentation of RUN_SETUP confused me. So I
> have a new patch that edits that as well.
>
> --
> RUN_SETUP_GENTLY and improve RUN_SETUP docs
>
> Signed-off-by: David Turner <dturner@xxxxxxxxxxx>
> ---
You do not want to have "Sorry about that..." in your final commit
log message. Please do the above this way if you wanted to:
Sorry about that ...
-- >8 --
Subject: docs: document RUN_SETUP_GENTLY and clarify RUN_SETUP
We only said what happens when we find the Git directory under
RUN_SETUP, without saying what happens otherwise.
Signed-off-by: ...
---
$DIFFSTAT
$PATCH
> Documentation/technical/api-builtin.txt | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/technical/api-builtin.txt
> b/Documentation/technical/api-builtin.txt
> index e3d6e7a..b250c1a 100644
> --- a/Documentation/technical/api-builtin.txt
> +++ b/Documentation/technical/api-builtin.txt
> @@ -23,10 +23,15 @@ where options is the bitwise-or of:
>
> `RUN_SETUP`::
>
> - Make sure there is a Git directory to work on, and if there is a
> - work tree, chdir to the top of it if the command was invoked
Your mailer ate all the whitespaces and folded the lines, it seems.
I'll fix it up and queue the result on 'pu', so please eyeball it
and holler if I made a silly mistake while doing the fixup.
Thanks.
> - in a subdirectory. If there is no work tree, no chdir() is
> - done.
> + If there is not a Git directory to work on, abort. If there
> + is a work tree, chdir to the top of it if the command was
> + invoked in a subdirectory. If there is no work tree, no
> + chdir() is done.
> +
> +`RUN_SETUP_GENTLY`::
> +
> + If there is a Git directory, chdir as per RUN_SETUP, otherwise,
> + don't chdir anywhere.
>
> `USE_PAGER`::
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html