path: root/Documentation/technical
diff options
Diffstat (limited to 'Documentation/technical')
4 files changed, 7 insertions, 135 deletions
diff --git a/Documentation/technical/api-builtin.txt b/Documentation/technical/api-builtin.txt
deleted file mode 100644
index 22a39b9..0000000
--- a/Documentation/technical/api-builtin.txt
+++ /dev/null
@@ -1,73 +0,0 @@
-builtin API
-Adding a new built-in
-There are 4 things to do to add a built-in command implementation to
-. Define the implementation of the built-in command `foo` with
- signature:
- int cmd_foo(int argc, const char **argv, const char *prefix);
-. Add the external declaration for the function to `builtin.h`.
-. Add the command to the `commands[]` table defined in `git.c`.
- The entry should look like:
- { "foo", cmd_foo, <options> },
-where options is the bitwise-or of:
- 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.
- If there is a Git directory, chdir as per RUN_SETUP, otherwise,
- don't chdir anywhere.
- If the standard output is connected to a tty, spawn a pager and
- feed our output to it.
- Make sure there is a work tree, i.e. the command cannot act
- on bare repositories.
- This only makes sense when `RUN_SETUP` is also set.
-. Add `builtin/foo.o` to `BUILTIN_OBJS` in `Makefile`.
-Additionally, if `foo` is a new command, there are 3 more things to do:
-. Add tests to `t/` directory.
-. Write documentation in `Documentation/git-foo.txt`.
-. Add an entry for `git-foo` to `command-list.txt`.
-. Add an entry for `/git-foo` to `.gitignore`.
-How a built-in is called
-The implementation `cmd_foo()` takes three parameters, `argc`, `argv,
-and `prefix`. The first two are similar to what `main()` of a
-standalone command would be called with.
-When `RUN_SETUP` is specified in the `commands[]` table, and when you
-were started from a subdirectory of the work tree, `cmd_foo()` is called
-after chdir(2) to the top of the work tree, and `prefix` gets the path
-to the subdirectory the command started from. This allows you to
-convert a user-supplied pathname (typically relative to that directory)
-to a pathname relative to the top of the work tree.
-The return value from `cmd_foo()` becomes the exit status of the
diff --git a/Documentation/technical/api-config.txt b/Documentation/technical/api-config.txt
index 20741f3..7a83a3a 100644
--- a/Documentation/technical/api-config.txt
+++ b/Documentation/technical/api-config.txt
@@ -187,6 +187,10 @@ Same as `git_config_bool`, except that integers are returned as-is, and
an `is_bool` flag is unset.
+Deprecated. Use `git_parse_maybe_bool` instead. They are exactly the
+same, except this function takes an unused argument `name`.
Same as `git_config_bool`, except that it returns -1 on error rather
than dying.
diff --git a/Documentation/technical/api-sub-process.txt b/Documentation/technical/api-sub-process.txt
deleted file mode 100644
index 793508c..0000000
--- a/Documentation/technical/api-sub-process.txt
+++ /dev/null
@@ -1,59 +0,0 @@
-sub-process API
-The sub-process API makes it possible to run background sub-processes
-for the entire lifetime of a Git invocation. If Git needs to communicate
-with an external process multiple times, then this can reduces the process
-invocation overhead. Git and the sub-process communicate through stdin and
-The sub-processes are kept in a hashmap by command name and looked up
-via the subprocess_find_entry function. If an existing instance can not
-be found then a new process should be created and started. When the
-parent git command terminates, all sub-processes are also terminated.
-This API is based on the run-command API.
-Data structures
-* `struct subprocess_entry`
-The sub-process structure. Members should not be accessed directly.
-'int(*subprocess_start_fn)(struct subprocess_entry *entry)'::
- User-supplied function to initialize the sub-process. This is
- typically used to negotiate the interface version and capabilities.
- Function to test two subprocess hashmap entries for equality.
- Start a subprocess and add it to the subprocess hashmap.
- Kill a subprocess and remove it from the subprocess hashmap.
- Find a subprocess in the subprocess hashmap.
- Get the underlying `struct child_process` from a subprocess.
- Helper function to read packets looking for the last "status=<foo>"
- key/value pair.
diff --git a/Documentation/technical/api-tree-walking.txt b/Documentation/technical/api-tree-walking.txt
index 14af37c..bde1862 100644
--- a/Documentation/technical/api-tree-walking.txt
+++ b/Documentation/technical/api-tree-walking.txt
@@ -55,9 +55,9 @@ Initializing
- Initialize a `tree_desc` and decode its first entry given the sha1 of
- a tree. Returns the `buffer` member if the sha1 is a valid tree
- identifier and NULL otherwise.
+ Initialize a `tree_desc` and decode its first entry given the
+ object ID of a tree. Returns the `buffer` member if the latter
+ is a valid tree identifier and NULL otherwise.