I've introduced this in 64c21ea5 (merged in cb7e0235), and since then, it hasn't been touched, except for 87857670 and d2b16f21 which fixed some typos in the documentation but not in the actual docstrings which it's based on.
Since (a correct version of) all this information is available in the docstrings and easily discoverable using `customize', there's no point in leaving it to languish in the docs. Signed-off-by: Pieter Praet <[email protected]> --- magit.texi | 141 ------------------------------------------------------------- 1 file changed, 141 deletions(-) diff --git a/magit.texi b/magit.texi index 8eaa3e7..7f18d82 100644 --- a/magit.texi +++ b/magit.texi @@ -60,7 +60,6 @@ maintain compatibility are still welcome. * Submodules:: * Using Magit Extensions:: * Using Git Directly:: -* Customization:: * Frequently Asked Questions:: * GNU Free Documentation License:: @end menu @@ -1139,146 +1138,6 @@ raw Git commands using @kbd{:}. This will prompt for a Git command, run it, and refresh the status buffer. The output can be viewed by typing @kbd{$}. - -@node Customization -@chapter Customization - -The following variables can be used to adapt Magit to your workflow: - -@table @code - -@item magit-git-executable -The name of the Git executable. - -@item magit-git-standard-options -Standard options when running Git. - -@item magit-repo-dirs -Directories containing Git repositories. - -Magit will look into these directories for Git repositories and offer -them as choices for @code{magit-status}. - -@item magit-repo-dirs-depth -The maximum depth to look for Git repos. - -When looking for a Git repository below the directories in -@code{magit-repo-dirs}, Magit will only descend this many levels deep. - -@item magit-save-some-buffers -Non-nil means that @code{magit-status} will save modified buffers -before running. Setting this to @code{t} will ask which buffers to -save, setting it to @code{'dontask} will save all modified buffers -without asking. - -@item magit-save-some-buffers-predicate -Specifies a predicate function on @code{magit-save-some-buffers} to -determine which unsaved buffers should be prompted for saving. - -@item magit-commit-all-when-nothing-staged -Determines what @code{magit-log-edit} does when nothing is staged. -Setting this to @code{nil} will make it do nothing, setting it to -@code{t} will arrange things so that the actual commit command will -use the @code{--all} option, setting it to @code{'ask} will first ask -for confirmation whether to do this, and setting it to -@code{'ask-stage} will cause all changes to be staged, after a -confirmation. - -@item magit-commit-signoff -When performing @code{git commit} adds @code{--signoff}. - -@item magit-log-cutoff-length -The maximum number of commits to show in the @code{log} and -@code{whazzup} buffers. - -@item magit-log-infinite-length -Number of log used to show as maximum for -@code{magit-log-cutoff-length}. - -@item magit-log-auto-more -Insert more log entries automatically when moving past the last entry. - -Only considered when moving past the last entry with @code{magit-goto-next-section}. - -@item magit-process-popup-time -Popup the process buffer if a command takes longer than this many -seconds. - -@item magit-revert-item-confirm -Require acknowledgment before reverting an item. - -@item magit-log-edit-confirm-cancellation -Require acknowledgment before canceling the log edit buffer. - -@item magit-remote-ref-format -What format to use for autocompleting refs, in particular for -remotes. - -Autocompletion is used by functions like @code{magit-checkout}, -@code{magit-interactive-rebase} and others which offer branch name -completion. - -The value @code{'name-then-remote} means remotes will be of the form -@code{name (remote)}, while the value @code{'remote-slash-name} means -that they'll be of the form @code{remote/name}. For example something -listed as @code{remotes/upstream/next} by @code{git branch -l -a} will -be offered as @code{next (upstream)} and @code{upstream/next}. - -@item magit-process-connection-type -Connection type used for the git process. - -@code{nil} mean pipe, it is usually faster and more efficient, and -work on cygwin. @code{t} mean pty, it enable magit to prompt for -passphrase when needed. - -@item magit-completing-read-function -Function to be called when requesting input from the user. - -@item magit-create-branch-behaviour -Where magit will create a new branch if not supplied a branchname or -ref. - -The value @code{'at-head} means a new branch will be created at the -tip of your current branch, while the value @code{'at-point} means -magit will try to find a valid reference at point... - -@item magit-status-buffer-switch-function -Function for @code{magit-status} to use for switching to the status -buffer. - -The function is given one argument, the status buffer. - -@item magit-rewrite-inclusive -Whether magit includes the selected base commit in a rewrite -operation. - -@code{t} means both the selected commit as well as any subsequent -commits will be rewritten. This is magit's default behaviour, -equivalent to @code{git rebase -i $@{REV~1@}} - -@verbatim - A'---B'---C'---D' - ^ -@end verbatim - -@code{nil} means the selected commit will be literally used as -@code{base}, so only subsequent commits will be rewritten. This is -consistent with git-rebase, equivalent to @code{git rebase -i -$@{REV@}}, yet more cumbersome to use from the status buffer. - -@verbatim - A---B'---C'---D' - ^ -@end verbatim - -@item magit-topgit-executable -The name of the TopGit executable. - -@item magit-topgit-branch-prefix -Convention prefix for topic branch creation. - -@end table - @node Frequently Asked Questions @chapter Frequently Asked Questions -- 1.7.11.1 -- --- You received this message because you are subscribed to the Google Groups "magit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
