From 7bd050fbdc12530213c7058bbba1b4a333ec7c02 Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Wed, 21 Sep 2011 23:32:22 -0700 Subject: [PATCH] Autogenerated HTML docs for v1.7.7-rc2-4-g5ec82 --- RelNotes/1.7.6.2.txt | 8 + RelNotes/1.7.6.3.txt | 24 ++ RelNotes/1.7.7.txt | 74 ++-- everyday.html | 202 ++++++++- git-add.html | 202 ++++++++- git-am.html | 202 ++++++++- git-annotate.html | 202 ++++++++- git-apply.html | 202 ++++++++- git-archimport.html | 202 ++++++++- git-archive.html | 202 ++++++++- git-bisect-lk2009.html | 202 ++++++++- git-bisect.html | 202 ++++++++- git-blame.html | 202 ++++++++- git-branch.html | 202 ++++++++- git-bundle.html | 202 ++++++++- git-cat-file.html | 202 ++++++++- git-check-attr.html | 202 ++++++++- git-check-ref-format.html | 202 ++++++++- git-checkout-index.html | 202 ++++++++- git-checkout.html | 202 ++++++++- git-cherry-pick.html | 202 ++++++++- git-cherry.html | 202 ++++++++- git-citool.html | 202 ++++++++- git-clean.html | 212 +++++++++- git-clean.txt | 10 +- git-clone.html | 202 ++++++++- git-commit-tree.html | 202 ++++++++- git-commit.html | 202 ++++++++- git-config.html | 202 ++++++++- git-count-objects.html | 202 ++++++++- git-cvsexportcommit.html | 202 ++++++++- git-cvsimport.html | 202 ++++++++- git-cvsserver.html | 202 ++++++++- git-daemon.html | 212 +++++++++- git-daemon.txt | 10 +- git-describe.html | 202 ++++++++- git-diff-files.html | 202 ++++++++- git-diff-index.html | 202 ++++++++- git-diff-tree.html | 202 ++++++++- git-diff.html | 202 ++++++++- git-difftool.html | 202 ++++++++- git-fast-export.html | 202 ++++++++- git-fast-import.html | 202 ++++++++- git-fetch-pack.html | 202 ++++++++- git-fetch.html | 202 ++++++++- git-filter-branch.html | 202 ++++++++- git-fmt-merge-msg.html | 202 ++++++++- git-for-each-ref.html | 202 ++++++++- git-format-patch.html | 211 +++++++++- git-format-patch.txt | 9 +- git-fsck-objects.html | 202 ++++++++- git-fsck.html | 202 ++++++++- git-gc.html | 202 ++++++++- git-get-tar-commit-id.html | 202 ++++++++- git-grep.html | 202 ++++++++- git-gui.html | 202 ++++++++- git-hash-object.html | 202 ++++++++- git-help.html | 202 ++++++++- git-http-backend.html | 202 ++++++++- git-http-fetch.html | 202 ++++++++- git-http-push.html | 202 ++++++++- git-imap-send.html | 202 ++++++++- git-index-pack.html | 202 ++++++++- git-init-db.html | 202 ++++++++- git-init.html | 202 ++++++++- git-instaweb.html | 202 ++++++++- git-log.html | 202 ++++++++- git-lost-found.html | 202 ++++++++- git-ls-files.html | 202 ++++++++- git-ls-remote.html | 202 ++++++++- git-ls-tree.html | 202 ++++++++- git-mailinfo.html | 202 ++++++++- git-mailsplit.html | 202 ++++++++- git-merge-base.html | 202 ++++++++- git-merge-file.html | 202 ++++++++- git-merge-index.html | 202 ++++++++- git-merge-one-file.html | 202 ++++++++- git-merge-tree.html | 202 ++++++++- git-merge.html | 202 ++++++++- git-mergetool--lib.html | 202 ++++++++- git-mergetool.html | 202 ++++++++- git-mktag.html | 202 ++++++++- git-mktree.html | 202 ++++++++- git-mv.html | 202 ++++++++- git-name-rev.html | 202 ++++++++- git-notes.html | 215 +++++++++- git-notes.txt | 7 +- git-pack-objects.html | 202 ++++++++- git-pack-redundant.html | 202 ++++++++- git-pack-refs.html | 202 ++++++++- git-parse-remote.html | 202 ++++++++- git-patch-id.html | 202 ++++++++- git-peek-remote.html | 202 ++++++++- git-prune-packed.html | 202 ++++++++- git-prune.html | 202 ++++++++- git-pull.html | 202 ++++++++- git-push.html | 212 +++++++++- git-push.txt | 6 + git-quiltimport.html | 202 ++++++++- git-read-tree.html | 202 ++++++++- git-rebase.html | 202 ++++++++- git-receive-pack.html | 212 ++++++++-- git-receive-pack.txt | 5 +- git-reflog.html | 202 ++++++++- git-relink.html | 202 ++++++++- git-remote-ext.html | 202 ++++++++- git-remote-fd.html | 202 ++++++++- git-remote-helpers.html | 452 ++++++++++++++++++--- git-remote-helpers.txt | 183 +++++++-- ...cvsexportcommit.html => git-remote-testgit.html | 392 +++++++++--------- git-remote-testgit.txt | 30 ++ git-remote.html | 202 ++++++++- git-repack.html | 202 ++++++++- git-replace.html | 202 ++++++++- git-repo-config.html | 202 ++++++++- git-request-pull.html | 202 ++++++++- git-rerere.html | 202 ++++++++- git-reset.html | 202 ++++++++- git-rev-list.html | 202 ++++++++- git-rev-parse.html | 202 ++++++++- git-revert.html | 202 ++++++++- git-rm.html | 202 ++++++++- git-send-email.html | 202 ++++++++- git-send-pack.html | 212 ++++++++-- git-send-pack.txt | 5 +- git-sh-i18n--envsubst.html | 202 ++++++++- git-sh-i18n.html | 202 ++++++++- git-sh-setup.html | 202 ++++++++- git-shell.html | 202 ++++++++- git-shortlog.html | 202 ++++++++- git-show-branch.html | 202 ++++++++- git-show-index.html | 202 ++++++++- git-show-ref.html | 202 ++++++++- git-show.html | 202 ++++++++- git-stage.html | 202 ++++++++- git-stash.html | 202 ++++++++- git-status.html | 202 ++++++++- git-stripspace.html | 202 ++++++++- git-submodule.html | 202 ++++++++- git-svn.html | 238 ++++++++++- git-svn.txt | 24 +- git-symbolic-ref.html | 202 ++++++++- git-tag.html | 202 ++++++++- git-tar-tree.html | 202 ++++++++- git-tools.html | 202 ++++++++- git-unpack-file.html | 202 ++++++++- git-unpack-objects.html | 202 ++++++++- git-update-index.html | 202 ++++++++- git-update-ref.html | 202 ++++++++- git-update-server-info.html | 202 ++++++++- git-upload-archive.html | 202 ++++++++- git-upload-pack.html | 202 ++++++++- git-var.html | 202 ++++++++- git-verify-pack.html | 202 ++++++++- git-verify-tag.html | 202 ++++++++- git-web--browse.html | 202 ++++++++- git-whatchanged.html | 202 ++++++++- git-write-tree.html | 202 ++++++++- git.html | 202 ++++++++- git.txt | 6 +- gitattributes.html | 202 ++++++++- gitcli.html | 202 ++++++++- gitcore-tutorial.html | 202 ++++++++- gitcvs-migration.html | 202 ++++++++- gitdiffcore.html | 202 ++++++++- gitglossary.html | 202 ++++++++- githooks.html | 202 ++++++++- gitignore.html | 202 ++++++++- gitk.html | 202 ++++++++- gitmodules.html | 202 ++++++++- gitnamespaces.html | 202 ++++++++- gitrepository-layout.html | 202 ++++++++- gitrevisions.html | 202 ++++++++- gittutorial-2.html | 202 ++++++++- gittutorial.html | 202 ++++++++- gitworkflows.html | 202 ++++++++- howto-index.html | 202 ++++++++- howto/maintain-git.txt | 13 +- howto/revert-branch-rebase.html | 202 ++++++++- howto/using-merge-subtree.html | 202 ++++++++- technical/api-allocation-growing.html | 202 ++++++++- technical/api-builtin.html | 202 ++++++++- technical/api-decorate.html | 202 ++++++++- technical/api-diff.html | 202 ++++++++- technical/api-directory-listing.html | 202 ++++++++- technical/api-gitattributes.html | 202 ++++++++- technical/api-grep.html | 202 ++++++++- technical/api-hash.html | 202 ++++++++- technical/api-history-graph.html | 202 ++++++++- technical/api-in-core-index.html | 202 ++++++++- technical/api-index.html | 202 ++++++++- technical/api-lockfile.html | 202 ++++++++- technical/api-merge.html | 202 ++++++++- technical/api-object-access.html | 202 ++++++++- technical/api-parse-options.html | 202 ++++++++- technical/api-quote.html | 202 ++++++++- technical/api-ref-iteration.html | 202 ++++++++- technical/api-remote.html | 202 ++++++++- technical/api-revision-walking.html | 202 ++++++++- technical/api-run-command.html | 202 ++++++++- technical/api-setup.html | 202 ++++++++- technical/api-sigchain.html | 202 ++++++++- technical/api-strbuf.html | 202 ++++++++- technical/api-string-list.html | 219 +++++++++- technical/api-string-list.txt | 10 + technical/api-tree-walking.html | 202 ++++++++- technical/api-xdiff-interface.html | 202 ++++++++- user-manual.html | 2 +- 208 files changed, 36167 insertions(+), 3406 deletions(-) create mode 100644 RelNotes/1.7.6.2.txt create mode 100644 RelNotes/1.7.6.3.txt copy git-cvsexportcommit.html => git-remote-testgit.html (51%) create mode 100644 git-remote-testgit.txt diff --git a/RelNotes/1.7.6.2.txt b/RelNotes/1.7.6.2.txt new file mode 100644 index 0000000000..67ae414965 --- /dev/null +++ b/RelNotes/1.7.6.2.txt @@ -0,0 +1,8 @@ +Git v1.7.6.2 Release Notes +========================== + +Fixes since v1.7.6.1 +-------------------- + + * v1.7.6.1 broke "git push --quiet"; it used to be a no-op against an old + version of Git running on the other end, but v1.7.6.1 made it abort. diff --git a/RelNotes/1.7.6.3.txt b/RelNotes/1.7.6.3.txt new file mode 100644 index 0000000000..95971831b9 --- /dev/null +++ b/RelNotes/1.7.6.3.txt @@ -0,0 +1,24 @@ +Git v1.7.6.3 Release Notes +========================== + +Fixes since v1.7.6.2 +-------------------- + + * "git -c var=value subcmd" misparsed the custom configuration when + value contained an equal sign. + + * "git fetch" had a major performance regression, wasting many + needless cycles in a repository where there is no submodules + present. This was especially bad, when there were many refs. + + * "git reflog $refname" did not default to the "show" subcommand as + the documentation advertised the command to do. + + * "git reset" did not leave meaningful log message in the reflog. + + * "git status --ignored" did not show ignored items when there is no + untracked items. + + * "git tag --contains $commit" was unnecessarily inefficient. + +Also contains minor fixes and documentation updates. diff --git a/RelNotes/1.7.7.txt b/RelNotes/1.7.7.txt index 82dc9292c3..f10ff28820 100644 --- a/RelNotes/1.7.7.txt +++ b/RelNotes/1.7.7.txt @@ -8,7 +8,7 @@ Updates since v1.7.6 * Interix, Cygwin and Minix ports got updated. - * Various updates git-p4 (in contrib/) and "git fast-import". + * Various updates to git-p4 (in contrib/), fast-import, and git-svn. * Gitweb learned to read from /etc/gitweb-common.conf when it exists, before reading from gitweb_config.perl or from /etc/gitweb.conf @@ -20,7 +20,7 @@ Updates since v1.7.6 platforms with 64-bit long, which has been corrected. * Git now recognizes loose objects written by other implementations that - uses non-standard window size for zlib deflation (e.g. Agit running on + use a non-standard window size for zlib deflation (e.g. Agit running on Android with 4kb window). We used to reject anything that was not deflated with 32kb window. @@ -28,71 +28,88 @@ Updates since v1.7.6 been improved, especially when a command that is not built-in was involved. - * "git am" learned to pass "--exclude=" option through to underlying + * "git am" learned to pass the "--exclude=" option through to underlying "git apply". - * You can now feed many empty lines before feeding a mbox file to + * You can now feed many empty lines before feeding an mbox file to "git am". * "git archive" can be told to pass the output to gzip compression and produce "archive.tar.gz". - * "git bisect" can be used in a bare repository (provided if the test + * "git bisect" can be used in a bare repository (provided that the test you perform per each iteration does not need a working tree, of course). * The length of abbreviated object names in "git branch -v" output - now honors core.abbrev configuration variable. + now honors the core.abbrev configuration variable. * "git check-attr" can take relative paths from the command line. - * "git check-attr" learned "--all" option to list the attributes for a + * "git check-attr" learned an "--all" option to list the attributes for a given path. * "git checkout" (both the code to update the files upon checking out a - different branch, the code to checkout specific set of files) learned + different branch and the code to checkout a specific set of files) learned to stream the data from object store when possible, without having to - read the entire contents of a file in memory first. An earlier round + read the entire contents of a file into memory first. An earlier round of this code that is not in any released version had a large leak but now it has been plugged. - * "git clone" can now take "--config key=value" option to set the + * "git clone" can now take a "--config key=value" option to set the repository configuration options that affect the initial checkout. * "git commit ..." now lets you feed relative pathspecs that - refer outside your current subdirectory. + refer to outside your current subdirectory. - * "git diff --stat" learned --stat-count option to limit the output of - diffstat report. + * "git diff --stat" learned a --stat-count option to limit the output of + a diffstat report. - * "git diff" learned "--histogram" option, to use a different diff + * "git diff" learned a "--histogram" option to use a different diff generation machinery stolen from jgit, which might give better performance. + * "git diff" had a weird worst case behaviour that can be triggered + when comparing files with potentially many places that could match. + * "git fetch", "git push" and friends no longer show connection - errors for addresses that couldn't be connected when at least one + errors for addresses that couldn't be connected to when at least one address succeeds (this is arguably a regression but a deliberate one). - * "git grep" learned --break and --heading options, to let users mimic - output format of "ack". + * "git grep" learned "--break" and "--heading" options, to let users mimic + the output format of "ack". - * "git grep" learned "-W" option that shows wider context using the same + * "git grep" learned a "-W" option that shows wider context using the same logic used by "git diff" to determine the hunk header. + * Invoking the low-level "git http-fetch" without "-a" option (which + git itself never did---normal users should not have to worry about + this) is now deprecated. + * The "--decorate" option to "git log" and its family learned to highlight grafted and replaced commits. * "git rebase master topci" no longer spews usage hints after giving - "fatal: no such branch: topci" error message. + the "fatal: no such branch: topci" error message. + + * The recursive merge strategy implementation got a fairly large + fix for many corner cases that may rarely happen in real world + projects (it has been verified that none of the 16000+ merges in + the Linux kernel history back to v2.6.12 is affected with the + corner case bugs this update fixes). - * "git stash" learned --include-untracked option. + * "git stash" learned an "--include-untracked option". * "git submodule update" used to stop at the first error updating a submodule; it now goes on to update other submodules that can be updated, and reports the ones with errors at the end. - * "git upload-pack" and "git receive-pack" learned to pretend only a + * "git push" can be told with the "--recurse-submodules=check" option to + refuse pushing of the supermodule, if any of its submodules' + commits hasn't been pushed out to their remotes. + + * "git upload-pack" and "git receive-pack" learned to pretend that only a subset of the refs exist in a repository. This may help a site to put many tiny repositories into one repository (this would not be useful for larger repositories as repacking would be problematic). @@ -101,7 +118,7 @@ Updates since v1.7.6 that is more efficient in reading objects in packfiles. * test scripts for gitweb tried to run even when CGI-related perl modules - are not installed; it now exits early when they are unavailable. + are not installed; they now exit early when the latter are unavailable. Also contains various documentation updates and minor miscellaneous changes. @@ -110,9 +127,13 @@ changes. Fixes since v1.7.6 ------------------ -Unless otherwise noted, all the fixes in 1.7.6.X maintenance track are +Unless otherwise noted, all fixes in the 1.7.6.X maintenance track are included in this release. + * The error reporting logic of "git am" when the command is fed a file + whose mail-storage format is unknown was fixed. + (merge dff4b0e gb/maint-am-patch-format-error-message later to 'maint'). + * "git branch --set-upstream @{-1} foo" did not expand @{-1} correctly. (merge e9d4f74 mg/branch-set-upstream-previous later to 'maint'). @@ -120,6 +141,11 @@ included in this release. of the branch that is currently checked out updated. (merge 55c4a67 ci/forbid-unwanted-current-branch-update later to 'maint'). + * "git check-ref-format --print" used to parrot a candidate string that + began with a slash (e.g. /refs/heads/master) without stripping it, to make + the result a suitably normalized string the caller can append to "$GIT_DIR/". + (merge f3738c1 mh/check-ref-format-print-normalize later to 'maint'). + * "git clone" failed to clone locally from a ".git" file that itself is not a directory but is a pointer to one. (merge 9b0ebc7 nd/maint-clone-gitdir later to 'maint'). @@ -140,7 +166,7 @@ included in this release. -- exec >/var/tmp/1 echo O=$(git describe master) -O=v1.7.6.1-415-g284daf2 +O=v1.7.7-rc2 git log --first-parent --oneline $O..master echo git shortlog --no-merges ^maint ^$O master diff --git a/everyday.html b/everyday.html index b6283670db..590e5ce280 100644 --- a/everyday.html +++ b/everyday.html @@ -3,7 +3,7 @@ - + Everyday GIT With 20 Commands Or So + +

[Individual Developer (Standalone)] commands are essential for @@ -1101,9 +1269,11 @@ upload to public HTTP server hosted by your ISP.

+
+

diff --git a/git-add.html b/git-add.html index 3b5469239e..89da623757 100644 --- a/git-add.html +++ b/git-add.html @@ -3,7 +3,7 @@ - + git-add(1) +
+

SYNOPSIS

@@ -931,9 +1099,11 @@ modifying the contents of context or removal lines

Part of the git(1) suite

+
+

diff --git a/git-am.html b/git-am.html index 64b2c9460c..387ee8fa95 100644 --- a/git-am.html +++ b/git-am.html @@ -3,7 +3,7 @@ - + git-am(1) +
+

SYNOPSIS

@@ -743,9 +911,11 @@ errors in the "From:" lines).

Part of the git(1) suite

+
+

diff --git a/git-annotate.html b/git-annotate.html index ad24f68720..fc41d764e5 100644 --- a/git-annotate.html +++ b/git-annotate.html @@ -3,7 +3,7 @@ - + git-annotate(1) +
+

SYNOPSIS

@@ -655,9 +823,11 @@ take effect.

Part of the git(1) suite

+
+

diff --git a/git-apply.html b/git-apply.html index 157de34e34..2a3a9fbb9c 100644 --- a/git-apply.html +++ b/git-apply.html @@ -3,7 +3,7 @@ - + git-apply(1) +
+

SYNOPSIS

@@ -822,9 +990,11 @@ subdirectory is checked and (if possible) updated.

Part of the git(1) suite

+
+

diff --git a/git-archimport.html b/git-archimport.html index c5204ac8a8..72d72f5a09 100644 --- a/git-archimport.html +++ b/git-archimport.html @@ -3,7 +3,7 @@ - + git-archimport(1) +
+

SYNOPSIS

@@ -556,9 +724,11 @@ patches that have been traded out-of-sequence between the branches.

Part of the git(1) suite

+
+

diff --git a/git-archive.html b/git-archive.html index 7547cf9fa2..16d14c0842 100644 --- a/git-archive.html +++ b/git-archive.html @@ -3,7 +3,7 @@ - + git-archive(1) +
+

SYNOPSIS

@@ -733,9 +901,11 @@ while archiving any tree in your $GIT_DIR/info/attributes file.

Part of the git(1) suite

+
+

diff --git a/git-bisect-lk2009.html b/git-bisect-lk2009.html index 1cd54833ac..78d7961a56 100644 --- a/git-bisect-lk2009.html +++ b/git-bisect-lk2009.html @@ -3,7 +3,7 @@ - + Fighting regressions with git bisect + +

Abstract

"git bisect" enables software users and developers to easily find the @@ -1557,9 +1725,11 @@ author to given a talk and for publishing this paper.

+
+

diff --git a/git-bisect.html b/git-bisect.html index 1bc92153dc..0efd5d2261 100644 --- a/git-bisect.html +++ b/git-bisect.html @@ -3,7 +3,7 @@ - + git-bisect(1) +
+

SYNOPSIS

@@ -757,9 +925,11 @@ required by git pack objects.

Part of the git(1) suite

+
+

diff --git a/git-blame.html b/git-blame.html index 91b34abc8a..cc86098102 100644 --- a/git-blame.html +++ b/git-blame.html @@ -3,7 +3,7 @@ - + git-blame(1) +
+

SYNOPSIS

@@ -997,9 +1165,11 @@ the email address.

Part of the git(1) suite

+
+

diff --git a/git-branch.html b/git-branch.html index e5021f8129..5b0573bf44 100644 --- a/git-branch.html +++ b/git-branch.html @@ -3,7 +3,7 @@ - + git-branch(1) +
+

SYNOPSIS

@@ -789,9 +957,11 @@ a branch?” in the Git User’s Manual.

Part of the git(1) suite

+
+

diff --git a/git-bundle.html b/git-bundle.html index 1a678a98eb..a091868d53 100644 --- a/git-bundle.html +++ b/git-bundle.html @@ -3,7 +3,7 @@ - + git-bundle(1) +
+

SYNOPSIS

@@ -626,9 +794,11 @@ references when fetching:

Part of the git(1) suite

+
+

diff --git a/git-cat-file.html b/git-cat-file.html index e4cec99c81..90c058eed4 100644 --- a/git-cat-file.html +++ b/git-cat-file.html @@ -3,7 +3,7 @@ - + git-cat-file(1) +
+

SYNOPSIS

@@ -552,9 +720,11 @@ for each object specified on stdin that does not exist in the repository:

Part of the git(1) suite

+
+

diff --git a/git-check-attr.html b/git-check-attr.html index 1c27f89e13..8090f56934 100644 --- a/git-check-attr.html +++ b/git-check-attr.html @@ -3,7 +3,7 @@ - + git-check-attr(1) +
+

SYNOPSIS

@@ -592,9 +760,11 @@ README: caveat: unspecified

Part of the git(1) suite

+
+

diff --git a/git-check-ref-format.html b/git-check-ref-format.html index ed6f78499a..95e868dd6c 100644 --- a/git-check-ref-format.html +++ b/git-check-ref-format.html @@ -3,7 +3,7 @@ - + git-check-ref-format(1) +
+

SYNOPSIS

@@ -550,9 +718,11 @@ die "we do not like '$newbranch' as a branch name."

Part of the git(1) suite

+
+

diff --git a/git-checkout-index.html b/git-checkout-index.html index b2345c7f96..9a00b4b5e0 100644 --- a/git-checkout-index.html +++ b/git-checkout-index.html @@ -3,7 +3,7 @@ - + git-checkout-index(1) +
+

SYNOPSIS

@@ -659,9 +827,11 @@ into the file .merged-Makefile.

Part of the git(1) suite

+
+

diff --git a/git-checkout.html b/git-checkout.html index 1cb4910599..c8e300fc3b 100644 --- a/git-checkout.html +++ b/git-checkout.html @@ -3,7 +3,7 @@ - + git-checkout(1) +
+

SYNOPSIS

@@ -957,9 +1125,11 @@ $ git add frotz

Part of the git(1) suite

+
+

diff --git a/git-cherry-pick.html b/git-cherry-pick.html index 1bbfbfc7bb..73713b8e6b 100644 --- a/git-cherry-pick.html +++ b/git-cherry-pick.html @@ -3,7 +3,7 @@ - + git-cherry-pick(1) +
+

SYNOPSIS

@@ -716,9 +884,11 @@ context lines.

Part of the git(1) suite

+
+

diff --git a/git-cherry.html b/git-cherry.html index 306906082c..5f01ea2102 100644 --- a/git-cherry.html +++ b/git-cherry.html @@ -3,7 +3,7 @@ - + git-cherry(1) +
+

SYNOPSIS

@@ -498,9 +666,11 @@ than pushing or pulling commits directly.

Part of the git(1) suite

+
+

diff --git a/git-citool.html b/git-citool.html index 7a51f593c2..1f254c8d83 100644 --- a/git-citool.html +++ b/git-citool.html @@ -3,7 +3,7 @@ - + git-citool(1) +
+

SYNOPSIS

@@ -432,9 +600,11 @@ See git-gui(1) for more details.

Part of the git(1) suite

+
+

diff --git a/git-clean.html b/git-clean.html index 5dc9bf525a..ceb402aaa1 100644 --- a/git-clean.html +++ b/git-clean.html @@ -3,7 +3,7 @@ - + git-clean(1) +
+

SYNOPSIS

@@ -486,9 +654,9 @@ are affected.

- Specify special exceptions to not be cleaned. Each <pattern> is - the same form as in $GIT_DIR/info/excludes and this option can be - given multiple times. + In addition to those found in .gitignore (per directory) and + $GIT_DIR/info/exclude, also consider these patterns to be in the + set of the ignore rules in effect.

@@ -496,7 +664,9 @@ are affected.

- Don’t use the ignore rules. This allows removing all untracked + Don’t use the standard ignore rules read from .gitignore (per + directory) and $GIT_DIR/info/exclude, but do still use the ignore + rules given with -e options. This allows removing all untracked files, including build products. This can be used (possibly in conjunction with git reset) to create a pristine working directory to test a clean build. @@ -517,9 +687,11 @@ are affected.

Part of the git(1) suite

+
+

diff --git a/git-clean.txt b/git-clean.txt index 974e04ef1a..79fb984144 100644 --- a/git-clean.txt +++ b/git-clean.txt @@ -47,12 +47,14 @@ OPTIONS -e :: --exclude=:: - Specify special exceptions to not be cleaned. Each is - the same form as in $GIT_DIR/info/excludes and this option can be - given multiple times. + In addition to those found in .gitignore (per directory) and + $GIT_DIR/info/exclude, also consider these patterns to be in the + set of the ignore rules in effect. -x:: - Don't use the ignore rules. This allows removing all untracked + Don't use the standard ignore rules read from .gitignore (per + directory) and $GIT_DIR/info/exclude, but do still use the ignore + rules given with `-e` options. This allows removing all untracked files, including build products. This can be used (possibly in conjunction with 'git reset') to create a pristine working directory to test a clean build. diff --git a/git-clone.html b/git-clone.html index db85d92cc4..8f9f090b32 100644 --- a/git-clone.html +++ b/git-clone.html @@ -3,7 +3,7 @@ - + git-clone(1) +
+

SYNOPSIS

@@ -918,9 +1086,11 @@ Create a repository on the kernel.org machine that borrows from Linus:

Part of the git(1) suite

+
+

diff --git a/git-commit-tree.html b/git-commit-tree.html index dc43e6758f..2be79d5e6a 100644 --- a/git-commit-tree.html +++ b/git-commit-tree.html @@ -3,7 +3,7 @@ - + git-commit-tree(1) +
+

SYNOPSIS

@@ -658,9 +826,11 @@ reversible operation.

Part of the git(1) suite

+
+

diff --git a/git-commit.html b/git-commit.html index e597767de9..8349fcfec3 100644 --- a/git-commit.html +++ b/git-commit.html @@ -3,7 +3,7 @@ - + git-commit(1) +
+

SYNOPSIS

@@ -1132,9 +1300,11 @@ information.

Part of the git(1) suite

+
+

diff --git a/git-config.html b/git-config.html index 809e624ea0..66361dc4d8 100644 --- a/git-config.html +++ b/git-config.html @@ -3,7 +3,7 @@ - + git-config(1) +
+

SYNOPSIS

@@ -4496,9 +4664,11 @@ web.browser

Part of the git(1) suite

+
+

diff --git a/git-count-objects.html b/git-count-objects.html index e43cb46d0d..3d5cce2ab8 100644 --- a/git-count-objects.html +++ b/git-count-objects.html @@ -3,7 +3,7 @@ - + git-count-objects(1) +
+

SYNOPSIS

@@ -448,9 +616,11 @@ them, to help you decide when it is a good time to repack.

Part of the git(1) suite

+
+

diff --git a/git-cvsexportcommit.html b/git-cvsexportcommit.html index 4f78390de8..6f5debc047 100644 --- a/git-cvsexportcommit.html +++ b/git-cvsexportcommit.html @@ -3,7 +3,7 @@ - + git-cvsexportcommit(1) +
+

SYNOPSIS

@@ -601,9 +769,11 @@ $ git cherry cvshead myhead | sed -n 's/^+ //p' | xargs -l1 git cvsexportcommit

Part of the git(1) suite

+
+

diff --git a/git-cvsimport.html b/git-cvsimport.html index 41d352504e..4681e700c8 100644 --- a/git-cvsimport.html +++ b/git-cvsimport.html @@ -3,7 +3,7 @@ - + git-cvsimport(1) +
+

SYNOPSIS

@@ -756,9 +924,11 @@ parsecvs, http://cgit.freedesktop.org/~keithp/parsecvs

Part of the git(1) suite

+
+

diff --git a/git-cvsserver.html b/git-cvsserver.html index 650c5596f9..cfdb45b98f 100644 --- a/git-cvsserver.html +++ b/git-cvsserver.html @@ -3,7 +3,7 @@ - + git-cvsserver(1) +
+

SYNOPSIS

SSH:

@@ -903,9 +1071,11 @@ and gitcvs.allbinary to "guess".

Part of the git(1) suite

+
+

diff --git a/git-daemon.html b/git-daemon.html index aa810eeaf8..2ae67b9c69 100644 --- a/git-daemon.html +++ b/git-daemon.html @@ -3,7 +3,7 @@ - + git-daemon(1) +
+

SYNOPSIS

@@ -543,8 +711,8 @@ git repositories.

- Timeout between the moment the connection is established and the - client request is received (typically a rather low value, since + Timeout (in seconds) between the moment the connection is established + and the client request is received (typically a rather low value, since that should be basically immediate).

@@ -553,9 +721,9 @@ git repositories.

- Timeout for specific client sub-requests. This includes the time - it takes for the server to process the sub-request and the time spent - waiting for the next client’s request. + Timeout (in seconds) for specific client sub-requests. This includes + the time it takes for the server to process the sub-request and the + time spent waiting for the next client’s request.

@@ -840,9 +1008,11 @@ services are performed.

Part of the git(1) suite

+
+

diff --git a/git-daemon.txt b/git-daemon.txt index ebd13be72e..69a1e4af9e 100644 --- a/git-daemon.txt +++ b/git-daemon.txt @@ -93,14 +93,14 @@ OPTIONS Listen on an alternative port. Incompatible with '--inetd' option. --init-timeout=:: - Timeout between the moment the connection is established and the - client request is received (typically a rather low value, since + Timeout (in seconds) between the moment the connection is established + and the client request is received (typically a rather low value, since that should be basically immediate). --timeout=:: - Timeout for specific client sub-requests. This includes the time - it takes for the server to process the sub-request and the time spent - waiting for the next client's request. + Timeout (in seconds) for specific client sub-requests. This includes + the time it takes for the server to process the sub-request and the + time spent waiting for the next client's request. --max-connections=:: Maximum number of concurrent clients, defaults to 32. Set it to diff --git a/git-describe.html b/git-describe.html index 0ff2d5734e..c6607eac5e 100644 --- a/git-describe.html +++ b/git-describe.html @@ -3,7 +3,7 @@ - + git-describe(1) +
+

SYNOPSIS

@@ -629,9 +797,11 @@ will be the smallest number of commits possible.

Part of the git(1) suite

+
+

diff --git a/git-diff-files.html b/git-diff-files.html index 70a06e1787..9a45751a6a 100644 --- a/git-diff-files.html +++ b/git-diff-files.html @@ -3,7 +3,7 @@ - + git-diff-files(1) +
+

SYNOPSIS

@@ -1762,9 +1930,11 @@ the pathname, but if that is NUL, the record will show two paths.

Part of the git(1) suite

+
+

diff --git a/git-diff-index.html b/git-diff-index.html index b46400976d..1544ae14e4 100644 --- a/git-diff-index.html +++ b/git-diff-index.html @@ -3,7 +3,7 @@ - + git-diff-index(1) +
+

SYNOPSIS

@@ -1840,9 +2008,11 @@ always have the special all-zero sha1.

Part of the git(1) suite

+
+

diff --git a/git-diff-tree.html b/git-diff-tree.html index ce1e86490d..3eb86d42e7 100644 --- a/git-diff-tree.html +++ b/git-diff-tree.html @@ -3,7 +3,7 @@ - + git-diff-tree(1) +
+

SYNOPSIS

@@ -2440,9 +2608,11 @@ the pathname, but if that is NUL, the record will show two paths.

Part of the git(1) suite

+
+

diff --git a/git-diff.html b/git-diff.html index 0d411a1a61..fbb1161ff4 100644 --- a/git-diff.html +++ b/git-diff.html @@ -3,7 +3,7 @@ - + git-diff(1) +
+

SYNOPSIS

@@ -1975,9 +2143,11 @@ Output diff in reverse.

Part of the git(1) suite

+
+

diff --git a/git-difftool.html b/git-difftool.html index cdaeff975d..e59c5dc2d2 100644 --- a/git-difftool.html +++ b/git-difftool.html @@ -3,7 +3,7 @@ - + git-difftool(1) +
+

SYNOPSIS

@@ -598,9 +766,11 @@ difftool.prompt

Part of the git(1) suite

+
+

diff --git a/git-fast-export.html b/git-fast-export.html index ebe0caf327..6832202778 100644 --- a/git-fast-export.html +++ b/git-fast-export.html @@ -3,7 +3,7 @@ - + git-fast-export(1) +
+

SYNOPSIS

@@ -601,9 +769,11 @@ a tag referencing a tree instead of a commit.

Part of the git(1) suite

+
+

diff --git a/git-fast-import.html b/git-fast-import.html index a1084e73b2..58d52efe98 100644 --- a/git-fast-import.html +++ b/git-fast-import.html @@ -3,7 +3,7 @@ - + git-fast-import(1) +
+

SYNOPSIS

@@ -1954,9 +2122,11 @@ compression.

Part of the git(1) suite

+
+

diff --git a/git-fetch-pack.html b/git-fetch-pack.html index 5fd6c1e5a0..732d7807c8 100644 --- a/git-fetch-pack.html +++ b/git-fetch-pack.html @@ -3,7 +3,7 @@ - + git-fetch-pack(1) +
+

SYNOPSIS

@@ -572,9 +740,11 @@ have a common ancestor commit.

Part of the git(1) suite

+
+

diff --git a/git-fetch.html b/git-fetch.html index 0820292021..e83a441034 100644 --- a/git-fetch.html +++ b/git-fetch.html @@ -3,7 +3,7 @@ - + git-fetch(1) +
+

SYNOPSIS

@@ -1043,9 +1211,11 @@ version.

Part of the git(1) suite

+
+

diff --git a/git-filter-branch.html b/git-filter-branch.html index 4afadbdde4..8ae859e027 100644 --- a/git-filter-branch.html +++ b/git-filter-branch.html @@ -3,7 +3,7 @@ - + git-filter-branch(1) +
+

SYNOPSIS

@@ -864,9 +1032,11 @@ Garbage collect all unreferenced objects with git gc --prune=now

Part of the git(1) suite

+
+

diff --git a/git-fmt-merge-msg.html b/git-fmt-merge-msg.html index f9cc1c75dc..8bb5e575c5 100644 --- a/git-fmt-merge-msg.html +++ b/git-fmt-merge-msg.html @@ -3,7 +3,7 @@ - + git-fmt-merge-msg(1) +
+

SYNOPSIS

@@ -523,9 +691,11 @@ merge.summary

Part of the git(1) suite

+
+

diff --git a/git-for-each-ref.html b/git-for-each-ref.html index 5822a3c046..9b581bcbf9 100644 --- a/git-for-each-ref.html +++ b/git-for-each-ref.html @@ -3,7 +3,7 @@ - + git-for-each-ref(1) +
+

SYNOPSIS

@@ -673,9 +841,11 @@ eval "$eval"

Part of the git(1) suite

+
+

diff --git a/git-format-patch.html b/git-format-patch.html index 3d3606c255..7d857d2ab5 100644 --- a/git-format-patch.html +++ b/git-format-patch.html @@ -3,7 +3,7 @@ - + git-format-patch(1) +
+

SYNOPSIS

@@ -1108,6 +1276,8 @@ will want to ensure that threading is disabled for git send-email.

<

Add a To: header to the email headers. This is in addition to any configured headers, and may be used multiple times. + The negated form --no-to discards all To: headers added so + far (from config or command line).

@@ -1117,6 +1287,8 @@ will want to ensure that threading is disabled for git send-email.

<

Add a Cc: header to the email headers. This is in addition to any configured headers, and may be used multiple times. + The negated form --no-cc discards all Cc: headers added so + far (from config or command line).

@@ -1126,7 +1298,10 @@ will want to ensure that threading is disabled for git send-email.

<

Add an arbitrary header to the email headers. This is in addition to any configured headers, and may be used multiple times. - For example, --add-header="Organization: git-foo" + For example, --add-header="Organization: git-foo". + The negated form --no-add-header discards all (To:, + Cc:, and custom) headers added so far from config or command + line.

@@ -1556,9 +1731,11 @@ as e-mailable patches:

Part of the git(1) suite

+
+

diff --git a/git-format-patch.txt b/git-format-patch.txt index d13c9b23f7..6ea9be775c 100644 --- a/git-format-patch.txt +++ b/git-format-patch.txt @@ -166,15 +166,22 @@ will want to ensure that threading is disabled for `git send-email`. --to=:: Add a `To:` header to the email headers. This is in addition to any configured headers, and may be used multiple times. + The negated form `--no-to` discards all `To:` headers added so + far (from config or command line). --cc=:: Add a `Cc:` header to the email headers. This is in addition to any configured headers, and may be used multiple times. + The negated form `--no-cc` discards all `Cc:` headers added so + far (from config or command line). --add-header=
:: Add an arbitrary header to the email headers. This is in addition to any configured headers, and may be used multiple times. - For example, `--add-header="Organization: git-foo"` + For example, `--add-header="Organization: git-foo"`. + The negated form `--no-add-header` discards *all* (`To:`, + `Cc:`, and custom) headers added so far from config or command + line. --cover-letter:: In addition to the patches, generate a cover letter file diff --git a/git-fsck-objects.html b/git-fsck-objects.html index f3d636486b..0a79e9848b 100644 --- a/git-fsck-objects.html +++ b/git-fsck-objects.html @@ -3,7 +3,7 @@ - + git-fsck-objects(1) +
+

SYNOPSIS

@@ -428,9 +596,11 @@ documentation of that command.

Part of the git(1) suite

+
+

diff --git a/git-fsck.html b/git-fsck.html index d3d6c9403a..0c7e02dc3b 100644 --- a/git-fsck.html +++ b/git-fsck.html @@ -3,7 +3,7 @@ - + git-fsck(1) +
+

SYNOPSIS

@@ -650,9 +818,11 @@ GIT_ALTERNATE_OBJECT_DIRECTORIES

Part of the git(1) suite

+
+

diff --git a/git-gc.html b/git-gc.html index f8836ac393..69c990bcb8 100644 --- a/git-gc.html +++ b/git-gc.html @@ -3,7 +3,7 @@ - + git-gc(1) +
+

SYNOPSIS

@@ -574,9 +742,11 @@ remove those references.

Part of the git(1) suite

+
+

diff --git a/git-get-tar-commit-id.html b/git-get-tar-commit-id.html index 273cccc8f7..c679af246d 100644 --- a/git-get-tar-commit-id.html +++ b/git-get-tar-commit-id.html @@ -3,7 +3,7 @@ - + git-get-tar-commit-id(1) +
+

SYNOPSIS

@@ -433,9 +601,11 @@ a tree ID instead of a commit ID or tag.

Part of the git(1) suite

+
+

diff --git a/git-grep.html b/git-grep.html index a51a127d29..26f12d46db 100644 --- a/git-grep.html +++ b/git-grep.html @@ -3,7 +3,7 @@ - + git-grep(1) +
+

SYNOPSIS

@@ -914,9 +1082,11 @@ grep.extendedRegexp

Part of the git(1) suite

+
+

diff --git a/git-gui.html b/git-gui.html index 32a9b5ef0c..97f0664dbd 100644 --- a/git-gui.html +++ b/git-gui.html @@ -3,7 +3,7 @@ - + git-gui(1) +
+

SYNOPSIS

@@ -599,9 +767,11 @@ of end users.

Part of the git(1) suite

+
+

diff --git a/git-hash-object.html b/git-hash-object.html index d2344ecedd..4e7871aac3 100644 --- a/git-hash-object.html +++ b/git-hash-object.html @@ -3,7 +3,7 @@ - + git-hash-object(1) +
+

SYNOPSIS

@@ -497,9 +665,11 @@ specified, it defaults to "blob".

Part of the git(1) suite

+
+

diff --git a/git-help.html b/git-help.html index fcb68d3ea2..184c833245 100644 --- a/git-help.html +++ b/git-help.html @@ -3,7 +3,7 @@ - + git-help(1) +
+

SYNOPSIS

@@ -607,9 +775,11 @@ See git-config(1) for more information about this.

Part of the git(1) suite

+
+

diff --git a/git-http-backend.html b/git-http-backend.html index 6ae2a41fa5..6fa06a0f43 100644 --- a/git-http-backend.html +++ b/git-http-backend.html @@ -3,7 +3,7 @@ - + git-http-backend(1) +
+

SYNOPSIS

@@ -647,9 +815,11 @@ invoked by the git-receive-pack.

Part of the git(1) suite

+
+

diff --git a/git-http-fetch.html b/git-http-fetch.html index fff80a533c..afe091e275 100644 --- a/git-http-fetch.html +++ b/git-http-fetch.html @@ -3,7 +3,7 @@ - + git-http-fetch(1) +
+

SYNOPSIS

@@ -506,9 +674,11 @@ commit-id

Part of the git(1) suite

+
+

diff --git a/git-http-push.html b/git-http-push.html index 820bacfc00..b8b3cd4bc5 100644 --- a/git-http-push.html +++ b/git-http-push.html @@ -3,7 +3,7 @@ - + git-http-push(1) +
+

SYNOPSIS

@@ -561,9 +729,11 @@ to disable the fast-forward check only on that ref.

Part of the git(1) suite

+
+

diff --git a/git-imap-send.html b/git-imap-send.html index 45b2202be3..2cb08c49a6 100644 --- a/git-imap-send.html +++ b/git-imap-send.html @@ -3,7 +3,7 @@ - + git-imap-send(1) +
+

SYNOPSIS

@@ -598,9 +766,11 @@ users may wish to visit this web page for more information:

Part of the git(1) suite

+
+

diff --git a/git-index-pack.html b/git-index-pack.html index 0be89609e7..b5909c87b9 100644 --- a/git-index-pack.html +++ b/git-index-pack.html @@ -3,7 +3,7 @@ - + git-index-pack(1) +
+

SYNOPSIS

@@ -536,9 +704,11 @@ mentioned above.

Part of the git(1) suite

+
+

diff --git a/git-init-db.html b/git-init-db.html index 8479779c57..172679dca1 100644 --- a/git-init-db.html +++ b/git-init-db.html @@ -3,7 +3,7 @@ - + git-init-db(1) +
+

SYNOPSIS

@@ -428,9 +596,11 @@ documentation of that command.

Part of the git(1) suite

+
+

diff --git a/git-init.html b/git-init.html index bc9e0e8b0a..360432d28f 100644 --- a/git-init.html +++ b/git-init.html @@ -3,7 +3,7 @@ - + git-init(1) +
+

SYNOPSIS

@@ -603,9 +771,11 @@ add all existing file to the index

Part of the git(1) suite

+
+

diff --git a/git-instaweb.html b/git-instaweb.html index b8023fad11..9b697fcb22 100644 --- a/git-instaweb.html +++ b/git-instaweb.html @@ -3,7 +3,7 @@ - + git-instaweb(1) +
+

SYNOPSIS

@@ -552,9 +720,11 @@ restart

Part of the git(1) suite

+
+

diff --git a/git-log.html b/git-log.html index 7c59523a2a..035484a565 100644 --- a/git-log.html +++ b/git-log.html @@ -3,7 +3,7 @@ - + git-log(1) +
+

SYNOPSIS

@@ -3197,9 +3365,11 @@ and overridden by the --notes=<ref> option.

Part of the git(1) suite

+
+

diff --git a/git-lost-found.html b/git-lost-found.html index 0d66a08982..cf5b1d010a 100644 --- a/git-lost-found.html +++ b/git-lost-found.html @@ -3,7 +3,7 @@ - + git-lost-found(1) +
+

SYNOPSIS

@@ -475,9 +643,11 @@ $ git rev-parse not-lost-anymore

Part of the git(1) suite

+
+

diff --git a/git-ls-files.html b/git-ls-files.html index 9ce73e8457..b3782ffe7d 100644 --- a/git-ls-files.html +++ b/git-ls-files.html @@ -3,7 +3,7 @@ - + git-ls-files(1) +
+

SYNOPSIS

@@ -816,9 +984,11 @@ pattern file appears in.

Part of the git(1) suite

+
+

diff --git a/git-ls-remote.html b/git-ls-remote.html index ef76e41569..5265c0aa20 100644 --- a/git-ls-remote.html +++ b/git-ls-remote.html @@ -3,7 +3,7 @@ - + git-ls-remote(1) +
+

SYNOPSIS

@@ -522,9 +690,11 @@ c5db5456ae3b0873fc659c19fafdde22313cc441 refs/tags/v0.99.2

Part of the git(1) suite

+
+

diff --git a/git-ls-tree.html b/git-ls-tree.html index 29c3895683..2432ec8f72 100644 --- a/git-ls-tree.html +++ b/git-ls-tree.html @@ -3,7 +3,7 @@ - + git-ls-tree(1) +
+

SYNOPSIS

@@ -578,9 +746,11 @@ with minimum width of 7 characters. Object size is given only for blobs

Part of the git(1) suite

+
+

diff --git a/git-mailinfo.html b/git-mailinfo.html index fe3f672ee8..37f6d6334d 100644 --- a/git-mailinfo.html +++ b/git-mailinfo.html @@ -3,7 +3,7 @@ - + git-mailinfo(1) +
+

SYNOPSIS

@@ -536,9 +704,11 @@ beginning of the proposed commit log message with a scissors line.

Part of the git(1) suite

+
+

diff --git a/git-mailsplit.html b/git-mailsplit.html index d672536b38..242dfb7bc4 100644 --- a/git-mailsplit.html +++ b/git-mailsplit.html @@ -3,7 +3,7 @@ - + git-mailsplit(1) +
+

SYNOPSIS

@@ -504,9 +672,11 @@ patches in the correct order.

Part of the git(1) suite

+
+

diff --git a/git-merge-base.html b/git-merge-base.html index ef643176bd..195e9050b6 100644 --- a/git-merge-base.html +++ b/git-merge-base.html @@ -3,7 +3,7 @@ - + git-merge-base(1) +
+

SYNOPSIS

@@ -544,9 +712,11 @@ it is unspecified which best one is output.

Part of the git(1) suite

+
+

diff --git a/git-merge-file.html b/git-merge-file.html index 683c666c84..97d647487c 100644 --- a/git-merge-file.html +++ b/git-merge-file.html @@ -3,7 +3,7 @@ - + git-merge-file(1) +
+

SYNOPSIS

@@ -529,9 +697,11 @@ implements all of RCS merge's functionality which is needed by

Part of the git(1) suite

+
+

diff --git a/git-merge-index.html b/git-merge-index.html index 78390ad3df..54d439ab7e 100644 --- a/git-merge-index.html +++ b/git-merge-index.html @@ -3,7 +3,7 @@ - + git-merge-index(1) +
+

SYNOPSIS

@@ -506,9 +674,11 @@ for the AA file, because it didn’t exist in the original, and thus

Part of the git(1) suite

+
+

diff --git a/git-merge-one-file.html b/git-merge-one-file.html index f524c3b824..ed42fa9e75 100644 --- a/git-merge-one-file.html +++ b/git-merge-one-file.html @@ -3,7 +3,7 @@ - + git-merge-one-file(1) +
+

SYNOPSIS

@@ -428,9 +596,11 @@ to resolve a merge after the trivial merge done with git read-tree -m.<

Part of the git(1) suite

+
+

diff --git a/git-merge-tree.html b/git-merge-tree.html index f14b097cb6..989c31976c 100644 --- a/git-merge-tree.html +++ b/git-merge-tree.html @@ -3,7 +3,7 @@ - + git-merge-tree(1) +
+

SYNOPSIS

@@ -435,9 +603,11 @@ entries that match the <branch1> tree.

Part of the git(1) suite

+
+

diff --git a/git-merge.html b/git-merge.html index 7226632ba6..426cf144a3 100644 --- a/git-merge.html +++ b/git-merge.html @@ -3,7 +3,7 @@ - + git-merge(1) +
+

SYNOPSIS

@@ -1277,9 +1445,11 @@ branch.<name>.mergeoptions

Part of the git(1) suite

+
+

diff --git a/git-mergetool--lib.html b/git-mergetool--lib.html index c65b597161..90ef38a609 100644 --- a/git-mergetool--lib.html +++ b/git-mergetool--lib.html @@ -3,7 +3,7 @@ - + git-mergetool--lib(1) +
+

SYNOPSIS

@@ -475,9 +643,11 @@ run_merge_tool

Part of the git(1) suite

+
+

diff --git a/git-mergetool.html b/git-mergetool.html index 01848ecd1c..24e0488b84 100644 --- a/git-mergetool.html +++ b/git-mergetool.html @@ -3,7 +3,7 @@ - + git-mergetool(1) +
+

SYNOPSIS

@@ -510,9 +678,11 @@ are successfully merged.

Part of the git(1) suite

+
+

diff --git a/git-mktag.html b/git-mktag.html index 3cb93e331b..c67d9a1d98 100644 --- a/git-mktag.html +++ b/git-mktag.html @@ -3,7 +3,7 @@ - + git-mktag(1) +
+

SYNOPSIS

@@ -445,9 +613,11 @@ care about, but that can be verified with gpg.

Part of the git(1) suite

+
+

diff --git a/git-mktree.html b/git-mktree.html index ad3e586ca3..bc6ebc033c 100644 --- a/git-mktree.html +++ b/git-mktree.html @@ -3,7 +3,7 @@ - + git-mktree(1) +
+

SYNOPSIS

@@ -465,9 +633,11 @@ built is written to the standard output.

Part of the git(1) suite

+
+

diff --git a/git-mv.html b/git-mv.html index 648ada24fc..76df1a7464 100644 --- a/git-mv.html +++ b/git-mv.html @@ -3,7 +3,7 @@ - + git-mv(1) +
+

SYNOPSIS

@@ -476,9 +644,11 @@ committed.

Part of the git(1) suite

+
+

diff --git a/git-name-rev.html b/git-name-rev.html index 4ca52e3481..55e6e33c96 100644 --- a/git-name-rev.html +++ b/git-name-rev.html @@ -3,7 +3,7 @@ - + git-name-rev(1) +
+

SYNOPSIS

@@ -514,9 +682,11 @@ not the context.

Part of the git(1) suite

+
+

diff --git a/git-notes.html b/git-notes.html index 0eff85ea2d..759a0ff1e7 100644 --- a/git-notes.html +++ b/git-notes.html @@ -3,7 +3,7 @@ - + git-notes(1) +
+

SYNOPSIS

@@ -622,8 +790,9 @@ get-ref

- Take the note message from the given blob object (for - example, another note). + Take the given blob object (for example, another note) as the + note message. (Use git notes copy <object> instead to + copy notes between objects.)

@@ -751,10 +920,10 @@ get-ref are taken from notes refs. A notes ref is usually a branch which contains "files" whose paths are the object names for the objects they describe, with some directory separators included for performance -reasons
[Permitted pathnames have the form +reasons
[Permitted pathnames have the form ab/cd/ef//abcdef…: a sequence of directory names of two hexadecimal digits each followed by a filename with the -rest of the object ID.]
.

+rest of the object ID.]
.

Every notes change creates a new commit at the specified notes ref. You can therefore inspect the history of the notes by invoking, e.g., git log -p notes/commits. Currently the commit message only records @@ -814,7 +983,9 @@ arbitrary files using git hash-object:

$ blob=$(git hash-object -w a.out) $ git notes --ref=built add -C "$blob" HEAD
-

Of course, it doesn’t make much sense to display non-text-format notes +

(You cannot simply use git notes --ref=built add -F a.out HEAD +because that is not binary-safe.) +Of course, it doesn’t make much sense to display non-text-format notes with git log, so if you use such notes, you’ll probably need to write some special-purpose tools to do something useful with them.

@@ -951,9 +1122,11 @@ Johan Herland <johan@herland.net>

Part of the git(7) suite

+
+

diff --git a/git-notes.txt b/git-notes.txt index 6a187f2e23..e8319eac69 100644 --- a/git-notes.txt +++ b/git-notes.txt @@ -142,8 +142,9 @@ OPTIONS -C :: --reuse-message=:: - Take the note message from the given blob object (for - example, another note). + Take the given blob object (for example, another note) as the + note message. (Use `git notes copy ` instead to + copy notes between objects.) -c :: --reedit-message=:: @@ -285,6 +286,8 @@ $ blob=$(git hash-object -w a.out) $ git notes --ref=built add -C "$blob" HEAD ------------ +(You cannot simply use `git notes --ref=built add -F a.out HEAD` +because that is not binary-safe.) Of course, it doesn't make much sense to display non-text-format notes with 'git log', so if you use such notes, you'll probably need to write some special-purpose tools to do something useful with them. diff --git a/git-pack-objects.html b/git-pack-objects.html index 26cd6691fc..711aeba2c2 100644 --- a/git-pack-objects.html +++ b/git-pack-objects.html @@ -3,7 +3,7 @@ - + git-pack-objects(1) + +

SYNOPSIS

@@ -764,9 +932,11 @@ So does git bundle (see git-bundle(1)) wh

Part of the git(1) suite

+
+

diff --git a/git-pack-redundant.html b/git-pack-redundant.html index b31aba5dba..5f97242113 100644 --- a/git-pack-redundant.html +++ b/git-pack-redundant.html @@ -3,7 +3,7 @@ - + git-pack-redundant(1) +
+

SYNOPSIS

@@ -471,9 +639,11 @@ git pack-redundant --all | xargs rm

Part of the git(1) suite

+
+

diff --git a/git-pack-refs.html b/git-pack-refs.html index 66c7775ea2..108c2013b5 100644 --- a/git-pack-refs.html +++ b/git-pack-refs.html @@ -3,7 +3,7 @@ - + git-pack-refs(1) +
+

SYNOPSIS

@@ -475,9 +643,11 @@ hierarchy after packing them. This option tells it not to.

Part of the git(1) suite

+
+

diff --git a/git-parse-remote.html b/git-parse-remote.html index a8650dae21..f66f7e837b 100644 --- a/git-parse-remote.html +++ b/git-parse-remote.html @@ -3,7 +3,7 @@ - + git-parse-remote(1) +
+

SYNOPSIS

@@ -430,9 +598,11 @@ to fetching, pulling and pushing.

Part of the git(1) suite

+
+

diff --git a/git-patch-id.html b/git-patch-id.html index 7fd75a13a4..d15a88afb2 100644 --- a/git-patch-id.html +++ b/git-patch-id.html @@ -3,7 +3,7 @@ - + git-patch-id(1) +
+

SYNOPSIS

@@ -449,9 +617,11 @@ This can be used to make a mapping from patch ID to commit ID.

Part of the git(1) suite

+
+

diff --git a/git-peek-remote.html b/git-peek-remote.html index eed52ff680..c2de23d28b 100644 --- a/git-peek-remote.html +++ b/git-peek-remote.html @@ -3,7 +3,7 @@ - + git-peek-remote(1) +
+

SYNOPSIS

@@ -467,9 +635,11 @@ git-peek-remote(1) Manual Page

Part of the git(1) suite

+
+

diff --git a/git-prune-packed.html b/git-prune-packed.html index 5d59f80956..27dba8ab09 100644 --- a/git-prune-packed.html +++ b/git-prune-packed.html @@ -3,7 +3,7 @@ - + git-prune-packed(1) +
+

SYNOPSIS

@@ -466,9 +634,11 @@ disk storage, etc.

Part of the git(1) suite

+
+

diff --git a/git-prune.html b/git-prune.html index 53b3d8b3cd..86a65219b9 100644 --- a/git-prune.html +++ b/git-prune.html @@ -3,7 +3,7 @@ - + git-prune(1) +
+

SYNOPSIS

@@ -522,9 +690,11 @@ many other housekeeping tasks.

Part of the git(1) suite

+
+

diff --git a/git-pull.html b/git-pull.html index b0926e151b..e8956cec6e 100644 --- a/git-pull.html +++ b/git-pull.html @@ -3,7 +3,7 @@ - + git-pull(1) +
+

SYNOPSIS

@@ -1441,9 +1609,11 @@ version.

Part of the git(1) suite

+
+

diff --git a/git-push.html b/git-push.html index 00be0e0ebb..e118547fb3 100644 --- a/git-push.html +++ b/git-push.html @@ -3,7 +3,7 @@ - + git-push(1) +
+

SYNOPSIS

@@ -655,6 +823,16 @@ useful if you write an alias or script around git push.

standard error stream is not directed to a terminal.

+
+--recurse-submodules=check +
+
+

+ Check whether all submodule commits used by the revisions to be + pushed are available on a remote tracking branch. Otherwise the + push will be aborted and the command will exit with non-zero status. +

+

GIT URLS

@@ -1222,9 +1400,11 @@ a git gc command on the origin repository.

Part of the git(1) suite

+
+

diff --git a/git-push.txt b/git-push.txt index 49c6e9fa51..aede48877f 100644 --- a/git-push.txt +++ b/git-push.txt @@ -162,6 +162,12 @@ useful if you write an alias or script around 'git push'. is specified. This flag forces progress status even if the standard error stream is not directed to a terminal. +--recurse-submodules=check:: + Check whether all submodule commits used by the revisions to be + pushed are available on a remote tracking branch. Otherwise the + push will be aborted and the command will exit with non-zero status. + + include::urls-remotes.txt[] OUTPUT diff --git a/git-quiltimport.html b/git-quiltimport.html index 289d95479d..5d1bcda5d7 100644 --- a/git-quiltimport.html +++ b/git-quiltimport.html @@ -3,7 +3,7 @@ - + git-quiltimport(1) +
+

SYNOPSIS

@@ -476,9 +644,11 @@ variable.

Part of the git(1) suite

+
+

diff --git a/git-read-tree.html b/git-read-tree.html index 4581d10b33..4dbb4370bd 100644 --- a/git-read-tree.html +++ b/git-read-tree.html @@ -3,7 +3,7 @@ - + git-read-tree(1) +
+

SYNOPSIS

@@ -937,9 +1105,11 @@ support.

Part of the git(1) suite

+
+

diff --git a/git-rebase.html b/git-rebase.html index 8f9b10afc8..9ea1f9645e 100644 --- a/git-rebase.html +++ b/git-rebase.html @@ -3,7 +3,7 @@ - + git-rebase(1) +
+

SYNOPSIS

@@ -1486,9 +1654,11 @@ reorder commits tend to produce counterintuitive results.

Part of the git(1) suite

+
+

diff --git a/git-receive-pack.html b/git-receive-pack.html index a138b8d188..574be8ebe2 100644 --- a/git-receive-pack.html +++ b/git-receive-pack.html @@ -3,7 +3,7 @@ - + git-receive-pack(1) +
+

SYNOPSIS

-
git-receive-pack [--quiet] <directory>
+
git-receive-pack <directory>
@@ -441,14 +609,6 @@ are not fast-forwards.

---quiet -
-
-

- Print only error messages. -

-
-
<directory>
@@ -573,9 +733,11 @@ exec git update-server-info

Part of the git(1) suite

+
+

diff --git a/git-receive-pack.txt b/git-receive-pack.txt index a3a1d8eea3..b1f7dc643a 100644 --- a/git-receive-pack.txt +++ b/git-receive-pack.txt @@ -9,7 +9,7 @@ git-receive-pack - Receive what is pushed into the repository SYNOPSIS -------- [verse] -'git-receive-pack' [--quiet] +'git-receive-pack' DESCRIPTION ----------- @@ -35,9 +35,6 @@ are not fast-forwards. OPTIONS ------- ---quiet:: - Print only error messages. - :: The repository to sync into. diff --git a/git-reflog.html b/git-reflog.html index a3108cfab0..50a11ed318 100644 --- a/git-reflog.html +++ b/git-reflog.html @@ -3,7 +3,7 @@ - + git-reflog(1) +
+

SYNOPSIS

@@ -534,9 +702,11 @@ them.

Part of the git(1) suite

+
+

diff --git a/git-relink.html b/git-relink.html index 91b4725ad8..1ab980bffa 100644 --- a/git-relink.html +++ b/git-relink.html @@ -3,7 +3,7 @@ - + git-relink(1) +
+

SYNOPSIS

@@ -451,9 +619,11 @@ repository will be replaced with a hardlink to the master repository.

Part of the git(1) suite

+
+

diff --git a/git-remote-ext.html b/git-remote-ext.html index 9bf004006c..7997579162 100644 --- a/git-remote-ext.html +++ b/git-remote-ext.html @@ -3,7 +3,7 @@ - + git-remote-ext(1) +
+

SYNOPSIS

@@ -612,9 +780,11 @@ begins with ext::. Examples:

Part of the git(1) suite

+
+

diff --git a/git-remote-fd.html b/git-remote-fd.html index a082576cac..51ff4eb5d3 100644 --- a/git-remote-fd.html +++ b/git-remote-fd.html @@ -3,7 +3,7 @@ - + git-remote-fd(1) +
+

SYNOPSIS

"fd::<infd>[,<outfd>][/<anything>]" (as URL)

@@ -493,9 +661,11 @@ GIT_TRANSLOOP_DEBUG

Part of the git(1) suite

+
+

diff --git a/git-remote-helpers.html b/git-remote-helpers.html index 85bf080429..7b66a7bb4c 100644 --- a/git-remote-helpers.html +++ b/git-remote-helpers.html @@ -3,7 +3,7 @@ - + git-remote-helpers(1) +
+

SYNOPSIS

@@ -431,20 +599,190 @@ standard input, and expects results from the helper’s standard output. Because a remote helper runs as an independent process from git, there is no need to re-link git to add a new helper, nor any need to link the helper with the implementation of git.

-

Every helper must support the "capabilities" command, which git will -use to determine what other commands the helper will accept. Other -commands generally concern facilities like discovering and updating -remote refs, transporting objects between the object database and -the remote repository, and updating the local object store.

-

Helpers supporting the fetch capability can discover refs from the -remote repository and transfer objects reachable from those refs to -the local object store. Helpers supporting the push capability can -transfer local objects to the remote repository and update remote refs.

+

Every helper must support the "capabilities" command, which git +uses to determine what other commands the helper will accept. Those +other commands can be used to discover and update remote refs, +transport objects between the object database and the remote repository, +and update the local object store.

Git comes with a "curl" family of remote helpers, that handle various transport protocols, such as git-remote-http, git-remote-https, git-remote-ftp and git-remote-ftps. They implement the capabilities fetch, option, and push.

+

INPUT FORMAT

+
+

Git sends the remote helper a list of commands on standard input, one +per line. The first command is always the capabilities command, in +response to which the remote helper must print a list of the +capabilities it supports (see below) followed by a blank line. The +response to the capabilities command determines what commands Git uses +in the remainder of the command stream.

+

The command stream is terminated by a blank line. In some cases +(indicated in the documentation of the relevant commands), this blank +line is followed by a payload in some other protocol (e.g., the pack +protocol), while in others it indicates the end of input.

+

Capabilities

+

Each remote helper is expected to support only a subset of commands. +The operations a helper supports are declared to git in the response +to the capabilities command (see COMMANDS, below).

+
+
+option +
+
+

+ For specifying settings like verbosity (how much output to + write to stderr) and depth (how much history is wanted in the + case of a shallow clone) that affect how other commands are + carried out. +

+
+
+connect +
+
+

+ For fetching and pushing using git’s native packfile protocol + that requires a bidirectional, full-duplex connection. +

+
+
+push +
+
+

+ For listing remote refs and pushing specified objects from the + local object store to remote refs. +

+
+
+fetch +
+
+

+ For listing remote refs and fetching the associated history to + the local object store. +

+
+
+import +
+
+

+ For listing remote refs and fetching the associated history as + a fast-import stream. +

+
+
+refspec <refspec> +
+
+

+ This modifies the import capability, allowing the produced + fast-import stream to modify refs in a private namespace + instead of writing to refs/heads or refs/remotes directly. + It is recommended that all importers providing the import + capability use this. +

+

A helper advertising the capability +refspec refs/heads/*:refs/svn/origin/branches/* +is saying that, when it is asked to import refs/heads/topic, the +stream it outputs will update the refs/svn/origin/branches/topic +ref.

+

This capability can be advertised multiple times. The first +applicable refspec takes precedence. The left-hand of refspecs +advertised with this capability must cover all refs reported by +the list command. If no refspec capability is advertised, +there is an implied refspec *:*.

+
+
+

Capabilities for Pushing

+
+
+connect +
+
+

+ Can attempt to connect to git receive-pack (for pushing), + git upload-pack, etc for communication using the + packfile protocol. +

+

Supported commands: connect.

+
+
+push +
+
+

+ Can discover remote refs and push local commits and the + history leading up to them to new or existing remote refs. +

+

Supported commands: list for-push, push.

+
+
+

If a helper advertises both connect and push, git will use +connect if possible and fall back to push if the helper requests +so when connecting (see the connect command under COMMANDS).

+

Capabilities for Fetching

+
+
+connect +
+
+

+ Can try to connect to git upload-pack (for fetching), + git receive-pack, etc for communication using the + packfile protocol. +

+

Supported commands: connect.

+
+
+fetch +
+
+

+ Can discover remote refs and transfer objects reachable from + them to the local object store. +

+

Supported commands: list, fetch.

+
+
+import +
+
+

+ Can discover remote refs and output objects reachable from + them as a stream in fast-import format. +

+

Supported commands: list, import.

+
+
+

If a helper advertises connect, git will use it if possible and +fall back to another capability if the helper requests so when +connecting (see the connect command under COMMANDS). +When choosing between fetch and import, git prefers fetch. +Other frontends may have some other order of preference.

+
+
+refspec <refspec> +
+
+

+ This modifies the import capability. +

+

A helper advertising +refspec refs/heads/*:refs/svn/origin/branches/* +in its capabilities is saying that, when it handles +import refs/heads/topic, the stream it outputs will update the +refs/svn/origin/branches/topic ref.

+

This capability can be advertised multiple times. The first +applicable refspec takes precedence. The left-hand of refspecs +advertised with this capability must cover all refs reported by +the list command. If no refspec capability is advertised, +there is an implied refspec *:*.

+
+
+

INVOCATION

Remote helper programs are invoked with one or (optionally) two @@ -542,8 +880,23 @@ suitably updated.

Pushes the given local <src> commit or branch to the remote branch described by <dst>. A batch sequence of - one or more push commands is terminated with a blank line. + one or more push commands is terminated with a blank line + (if there is only one reference to push, a single push command + is followed by a blank line). For example, the following would + be two batches of push, the first asking the remote-helper + to push the local ref master to the remote ref master and + the local HEAD to the remote branch, and the second + asking to push ref foo to ref bar (forced update requested + by the +).

+
+
+
push refs/heads/master:refs/heads/master
+push HEAD:refs/heads/branch
+\n
+push +refs/heads/foo:refs/heads/bar
+\n
+

Zero or more protocol options may be entered after the last push command, before the batch’s terminating blank line.

When the push is complete, outputs one or more ok <dst> or @@ -568,6 +921,10 @@ style string if it contains an LF.

Especially useful for interoperability with a foreign versioning system.

+

Just like push, a batch sequence of one or more import is +terminated with a blank line. For each batch of import, the remote +helper should produce a fast-import stream terminated by a done +command.

Supported if the helper has the "import" capability.

@@ -596,46 +953,6 @@ completing a valid response for the current command.

Additional commands may be supported, as may be determined from capabilities reported by the helper.

-

CAPABILITIES

-
-
-
-fetch -
-
-option -
-
-push -
-
-import -
-
-connect -
-
-

- This helper supports the corresponding command with the same name. -

-
-
-refspec spec -
-
-

- When using the import command, expect the source ref to have - been written to the destination ref. The earliest applicable - refspec takes precedence. For example - "refs/heads/*:refs/svn/origin/branches/*" means - that, after an "import refs/heads/name", the script has written to - refs/svn/origin/branches/name. If this capability is used at - all, it must cover all refs reported by the list command; if - it is not used, it is effectively "*:*" -

-
-
-

REF LIST ATTRIBUTES

@@ -728,14 +1045,17 @@ capabilities reported by the helper.

SEE ALSO

GIT

Part of the git(1) suite

+
+

diff --git a/git-remote-helpers.txt b/git-remote-helpers.txt index 4f83dea5a3..674797cd83 100644 --- a/git-remote-helpers.txt +++ b/git-remote-helpers.txt @@ -24,22 +24,141 @@ output. Because a remote helper runs as an independent process from git, there is no need to re-link git to add a new helper, nor any need to link the helper with the implementation of git. -Every helper must support the "capabilities" command, which git will -use to determine what other commands the helper will accept. Other -commands generally concern facilities like discovering and updating -remote refs, transporting objects between the object database and -the remote repository, and updating the local object store. - -Helpers supporting the 'fetch' capability can discover refs from the -remote repository and transfer objects reachable from those refs to -the local object store. Helpers supporting the 'push' capability can -transfer local objects to the remote repository and update remote refs. +Every helper must support the "capabilities" command, which git +uses to determine what other commands the helper will accept. Those +other commands can be used to discover and update remote refs, +transport objects between the object database and the remote repository, +and update the local object store. Git comes with a "curl" family of remote helpers, that handle various transport protocols, such as 'git-remote-http', 'git-remote-https', 'git-remote-ftp' and 'git-remote-ftps'. They implement the capabilities 'fetch', 'option', and 'push'. +INPUT FORMAT +------------ + +Git sends the remote helper a list of commands on standard input, one +per line. The first command is always the 'capabilities' command, in +response to which the remote helper must print a list of the +capabilities it supports (see below) followed by a blank line. The +response to the capabilities command determines what commands Git uses +in the remainder of the command stream. + +The command stream is terminated by a blank line. In some cases +(indicated in the documentation of the relevant commands), this blank +line is followed by a payload in some other protocol (e.g., the pack +protocol), while in others it indicates the end of input. + +Capabilities +~~~~~~~~~~~~ + +Each remote helper is expected to support only a subset of commands. +The operations a helper supports are declared to git in the response +to the `capabilities` command (see COMMANDS, below). + +'option':: + For specifying settings like `verbosity` (how much output to + write to stderr) and `depth` (how much history is wanted in the + case of a shallow clone) that affect how other commands are + carried out. + +'connect':: + For fetching and pushing using git's native packfile protocol + that requires a bidirectional, full-duplex connection. + +'push':: + For listing remote refs and pushing specified objects from the + local object store to remote refs. + +'fetch':: + For listing remote refs and fetching the associated history to + the local object store. + +'import':: + For listing remote refs and fetching the associated history as + a fast-import stream. + +'refspec' :: + This modifies the 'import' capability, allowing the produced + fast-import stream to modify refs in a private namespace + instead of writing to refs/heads or refs/remotes directly. + It is recommended that all importers providing the 'import' + capability use this. ++ +A helper advertising the capability +`refspec refs/heads/{asterisk}:refs/svn/origin/branches/{asterisk}` +is saying that, when it is asked to `import refs/heads/topic`, the +stream it outputs will update the `refs/svn/origin/branches/topic` +ref. ++ +This capability can be advertised multiple times. The first +applicable refspec takes precedence. The left-hand of refspecs +advertised with this capability must cover all refs reported by +the list command. If no 'refspec' capability is advertised, +there is an implied `refspec {asterisk}:{asterisk}`. + +Capabilities for Pushing +~~~~~~~~~~~~~~~~~~~~~~~~ +'connect':: + Can attempt to connect to 'git receive-pack' (for pushing), + 'git upload-pack', etc for communication using the + packfile protocol. ++ +Supported commands: 'connect'. + +'push':: + Can discover remote refs and push local commits and the + history leading up to them to new or existing remote refs. ++ +Supported commands: 'list for-push', 'push'. + +If a helper advertises both 'connect' and 'push', git will use +'connect' if possible and fall back to 'push' if the helper requests +so when connecting (see the 'connect' command under COMMANDS). + +Capabilities for Fetching +~~~~~~~~~~~~~~~~~~~~~~~~~ +'connect':: + Can try to connect to 'git upload-pack' (for fetching), + 'git receive-pack', etc for communication using the + packfile protocol. ++ +Supported commands: 'connect'. + +'fetch':: + Can discover remote refs and transfer objects reachable from + them to the local object store. ++ +Supported commands: 'list', 'fetch'. + +'import':: + Can discover remote refs and output objects reachable from + them as a stream in fast-import format. ++ +Supported commands: 'list', 'import'. + +If a helper advertises 'connect', git will use it if possible and +fall back to another capability if the helper requests so when +connecting (see the 'connect' command under COMMANDS). +When choosing between 'fetch' and 'import', git prefers 'fetch'. +Other frontends may have some other order of preference. + +'refspec' :: + This modifies the 'import' capability. ++ +A helper advertising +`refspec refs/heads/{asterisk}:refs/svn/origin/branches/{asterisk}` +in its capabilities is saying that, when it handles +`import refs/heads/topic`, the stream it outputs will update the +`refs/svn/origin/branches/topic` ref. ++ +This capability can be advertised multiple times. The first +applicable refspec takes precedence. The left-hand of refspecs +advertised with this capability must cover all refs reported by +the list command. If no 'refspec' capability is advertised, +there is an implied `refspec {asterisk}:{asterisk}`. + INVOCATION ---------- @@ -122,7 +241,22 @@ Supported if the helper has the "fetch" capability. 'push' +::: Pushes the given local commit or branch to the remote branch described by . A batch sequence of - one or more push commands is terminated with a blank line. + one or more 'push' commands is terminated with a blank line + (if there is only one reference to push, a single 'push' command + is followed by a blank line). For example, the following would + be two batches of 'push', the first asking the remote-helper + to push the local ref 'master' to the remote ref 'master' and + the local 'HEAD' to the remote 'branch', and the second + asking to push ref 'foo' to ref 'bar' (forced update requested + by the '+'). ++ +------------ +push refs/heads/master:refs/heads/master +push HEAD:refs/heads/branch +\n +push +refs/heads/foo:refs/heads/bar +\n +------------ + Zero or more protocol options may be entered after the last 'push' command, before the batch's terminating blank line. @@ -147,6 +281,11 @@ Supported if the helper has the "push" capability. Especially useful for interoperability with a foreign versioning system. + +Just like 'push', a batch sequence of one or more 'import' is +terminated with a blank line. For each batch of 'import', the remote +helper should produce a fast-import stream terminated by a 'done' +command. ++ Supported if the helper has the "import" capability. 'connect' :: @@ -171,26 +310,6 @@ completing a valid response for the current command. Additional commands may be supported, as may be determined from capabilities reported by the helper. -CAPABILITIES ------------- - -'fetch':: -'option':: -'push':: -'import':: -'connect':: - This helper supports the corresponding command with the same name. - -'refspec' 'spec':: - When using the import command, expect the source ref to have - been written to the destination ref. The earliest applicable - refspec takes precedence. For example - "refs/heads/{asterisk}:refs/svn/origin/branches/{asterisk}" means - that, after an "import refs/heads/name", the script has written to - refs/svn/origin/branches/name. If this capability is used at - all, it must cover all refs reported by the list command; if - it is not used, it is effectively "{asterisk}:{asterisk}" - REF LIST ATTRIBUTES ------------------- @@ -243,6 +362,8 @@ SEE ALSO -------- linkgit:git-remote[1] +linkgit:git-remote-testgit[1] + GIT --- Part of the linkgit:git[1] suite diff --git a/git-cvsexportcommit.html b/git-remote-testgit.html similarity index 51% copy from git-cvsexportcommit.html copy to git-remote-testgit.html index 4f78390de8..bd981f733a 100644 --- a/git-cvsexportcommit.html +++ b/git-remote-testgit.html @@ -3,8 +3,8 @@ - -git-cvsexportcommit(1) + +git-remote-testgit(1) + +

SYNOPSIS

-
git cvsexportcommit [-h] [-u] [-v] [-c] [-P] [-p] [-a] [-d cvsroot] - [-w cvsworkdir] [-W] [-f] [-m msgprefix] [PARENTCOMMIT] COMMITID
+
git clone testgit::<source-repo> [<destination>]

DESCRIPTION

-

Exports a commit from GIT to a CVS checkout, making it easier -to merge patches from a git repository into a CVS repository.

-

Specify the name of a CVS checkout using the -w switch or execute it -from the root of the CVS working copy. In the latter case GIT_DIR must -be defined. See examples below.

-

It does its best to do the safe thing, it will check that the files are -unchanged and up to date in the CVS checkout, and it will not autocommit -by default.

-

Supports file additions, removals, and commits that affect binary files.

-

If the commit is a merge commit, you must tell git cvsexportcommit what -parent the changeset should be done against.

+

This command is a simple remote-helper, that is used both as a +testcase for the remote-helper functionality, and as an example to +show remote-helper authors one possible implementation.

+

The best way to learn more is to read the comments and source code in +git-remote-testgit.py.

-

OPTIONS

+

SEE ALSO

-
-
--c -
-
-

- Commit automatically if the patch applied cleanly. It will not - commit if any hunks fail to apply or there were other problems. -

-
-
--p -
-
-

- Be pedantic (paranoid) when applying patches. Invokes patch with - --fuzz=0 -

-
-
--a -
-
-

- Add authorship information. Adds Author line, and Committer (if - different from Author) to the message. -

-
-
--d -
-
-

- Set an alternative CVSROOT to use. This corresponds to the CVS - -d parameter. Usually users will not want to set this, except - if using CVS in an asymmetric fashion. -

-
-
--f -
-
-

- Force the merge even if the files are not up to date. -

-
-
--P -
-
-

- Force the parent commit, even if it is not a direct parent. -

-
-
--m -
-
-

- Prepend the commit message with the provided prefix. - Useful for patch series and the like. -

-
-
--u -
-
-

- Update affected files from CVS repository before attempting export. -

-
-
--k -
-
-

- Reverse CVS keyword expansion (e.g. $Revision: 1.2.3.4$ - becomes $Revision$) in working CVS checkout before applying patch. -

-
-
--w -
-
-

- Specify the location of the CVS checkout to use for the export. This - option does not require GIT_DIR to be set before execution if the - current directory is within a git repository. The default is the - value of cvsexportcommit.cvsdir. -

-
-
--W -
-
-

- Tell cvsexportcommit that the current working directory is not only - a Git checkout, but also the CVS checkout. Therefore, Git will - reset the working directory to the parent commit before proceeding. -

-
-
--v -
-
-

- Verbose. -

-
-
-
-

CONFIGURATION

-
-
-
-cvsexportcommit.cvsdir -
-
-

- The default location of the CVS checkout to use for the export. -

-
-
-
-

EXAMPLES

-
-
-
-Merge one patch into CVS -
-
-
-
-
$ export GIT_DIR=~/project/.git
-$ cd ~/project_cvs_checkout
-$ git cvsexportcommit -v <commit-sha1>
-$ cvs commit -F .msg <files>
-
-
-
-Merge one patch into CVS (-c and -w options). The working directory is within the Git Repo -
-
-
-
-
        $ git cvsexportcommit -v -c -w ~/project_cvs_checkout <commit-sha1>
-
-
-
-Merge pending patches into CVS automatically — only if you really know what you are doing -
-
-
-
-
$ export GIT_DIR=~/project/.git
-$ cd ~/project_cvs_checkout
-$ git cherry cvshead myhead | sed -n 's/^+ //p' | xargs -l1 git cvsexportcommit -c -p -v
-
-
-
+

GIT

Part of the git(1) suite

+
+

diff --git a/git-remote-testgit.txt b/git-remote-testgit.txt new file mode 100644 index 0000000000..2a67d456a3 --- /dev/null +++ b/git-remote-testgit.txt @@ -0,0 +1,30 @@ +git-remote-testgit(1) +===================== + +NAME +---- +git-remote-testgit - Example remote-helper + + +SYNOPSIS +-------- +[verse] +git clone testgit:: [] + +DESCRIPTION +----------- + +This command is a simple remote-helper, that is used both as a +testcase for the remote-helper functionality, and as an example to +show remote-helper authors one possible implementation. + +The best way to learn more is to read the comments and source code in +'git-remote-testgit.py'. + +SEE ALSO +-------- +linkgit:git-remote-helpers[1] + +GIT +--- +Part of the linkgit:git[1] suite diff --git a/git-remote.html b/git-remote.html index 55f2f3a9fc..b613e37953 100644 --- a/git-remote.html +++ b/git-remote.html @@ -3,7 +3,7 @@ - + git-remote(1) + +

SYNOPSIS

@@ -658,9 +826,11 @@ $ git merge origin

Part of the git(1) suite

+
+

diff --git a/git-repack.html b/git-repack.html index d9d185c90d..688b5a29f0 100644 --- a/git-repack.html +++ b/git-repack.html @@ -3,7 +3,7 @@ - + git-repack(1) +
+

SYNOPSIS

@@ -594,9 +762,11 @@ as needed in that case.

Part of the git(1) suite

+
+

diff --git a/git-replace.html b/git-replace.html index 9e539fda39..814cdc84dc 100644 --- a/git-replace.html +++ b/git-replace.html @@ -3,7 +3,7 @@ - + git-replace(1) +
+

SYNOPSIS

@@ -502,9 +670,11 @@ replaced by a commit).

Part of the git(1) suite

+
+

diff --git a/git-repo-config.html b/git-repo-config.html index a1da29ef2d..eb9cb9be81 100644 --- a/git-repo-config.html +++ b/git-repo-config.html @@ -3,7 +3,7 @@ - + git-repo-config(1) +
+

SYNOPSIS

@@ -428,9 +596,11 @@ documentation of that command.

Part of the git(1) suite

+
+

diff --git a/git-request-pull.html b/git-request-pull.html index 8e02a829ad..7f958c200e 100644 --- a/git-request-pull.html +++ b/git-request-pull.html @@ -3,7 +3,7 @@ - + git-request-pull(1) +
+

SYNOPSIS

@@ -465,9 +633,11 @@ the given URL in the generated summary.

Part of the git(1) suite

+
+

diff --git a/git-rerere.html b/git-rerere.html index 12e22b2890..789c15dbf9 100644 --- a/git-rerere.html +++ b/git-rerere.html @@ -3,7 +3,7 @@ - + git-rerere(1) +
+

SYNOPSIS

@@ -628,9 +796,11 @@ conflict.

Part of the git(1) suite

+
+

diff --git a/git-reset.html b/git-reset.html index 0f2411410e..19cd467773 100644 --- a/git-reset.html +++ b/git-reset.html @@ -3,7 +3,7 @@ - + git-reset(1) +
+

SYNOPSIS

@@ -999,9 +1167,11 @@ entries:

Part of the git(1) suite

+
+

diff --git a/git-rev-list.html b/git-rev-list.html index 72b16f7892..8989158cf3 100644 --- a/git-rev-list.html +++ b/git-rev-list.html @@ -3,7 +3,7 @@ - + git-rev-list(1) +
+

SYNOPSIS

@@ -2054,9 +2222,11 @@ $ git log -2 --pretty=%h 4da45bef

Part of the git(1) suite

+
+

diff --git a/git-rev-parse.html b/git-rev-parse.html index f42163485e..632fbcce96 100644 --- a/git-rev-parse.html +++ b/git-rev-parse.html @@ -3,7 +3,7 @@ - + git-rev-parse(1) +
+

SYNOPSIS

@@ -1231,9 +1399,11 @@ Same as above:

Part of the git(1) suite

+
+

diff --git a/git-revert.html b/git-revert.html index 7bdad37a6d..17bd68ca2f 100644 --- a/git-revert.html +++ b/git-revert.html @@ -3,7 +3,7 @@ - + git-revert(1) +
+

SYNOPSIS

@@ -582,9 +750,11 @@ effect to your index in a row.

Part of the git(1) suite

+
+

diff --git a/git-rm.html b/git-rm.html index d7b5d4fe8c..b968a9eaf0 100644 --- a/git-rm.html +++ b/git-rm.html @@ -3,7 +3,7 @@ - + git-rm(1) +
+

SYNOPSIS

@@ -614,9 +782,11 @@ of files and subdirectories under the Documentation/ directory.

Part of the git(1) suite

+
+

diff --git a/git-send-email.html b/git-send-email.html index bbe332b1dc..e25e5e3c31 100644 --- a/git-send-email.html +++ b/git-send-email.html @@ -3,7 +3,7 @@ - + git-send-email(1) +
+

SYNOPSIS

@@ -1008,9 +1176,11 @@ $ git send-email outgoing/*

Part of the git(1) suite

+
+

diff --git a/git-send-pack.html b/git-send-pack.html index a865cbc07c..c67c0008a3 100644 --- a/git-send-pack.html +++ b/git-send-pack.html @@ -3,7 +3,7 @@ - + git-send-pack(1) +
+

SYNOPSIS

-
git send-pack [--all] [--dry-run] [--force] [--receive-pack=<git-receive-pack>] [--quiet] [--verbose] [--thin] [<host>:]<directory> [<ref>…]
+
git send-pack [--all] [--dry-run] [--force] [--receive-pack=<git-receive-pack>] [--verbose] [--thin] [<host>:]<directory> [<ref>…]
@@ -478,14 +646,6 @@ updates it from the current repository, sending named refs.

---quiet -
-
-

- Print only error messages. -

-
-
--verbose
@@ -596,9 +756,11 @@ to disable the fast-forward check only on that ref.

Part of the git(1) suite

+
+

diff --git a/git-send-pack.txt b/git-send-pack.txt index bed9e1f097..bd3eaa69bf 100644 --- a/git-send-pack.txt +++ b/git-send-pack.txt @@ -9,7 +9,7 @@ git-send-pack - Push objects over git protocol to another repository SYNOPSIS -------- [verse] -'git send-pack' [--all] [--dry-run] [--force] [--receive-pack=] [--quiet] [--verbose] [--thin] [:] [...] +'git send-pack' [--all] [--dry-run] [--force] [--receive-pack=] [--verbose] [--thin] [:] [...] DESCRIPTION ----------- @@ -45,9 +45,6 @@ OPTIONS the remote repository can lose commits; use it with care. ---quiet:: - Print only error messages. - --verbose:: Run verbosely. diff --git a/git-sh-i18n--envsubst.html b/git-sh-i18n--envsubst.html index 8dc9215388..356bc41024 100644 --- a/git-sh-i18n--envsubst.html +++ b/git-sh-i18n--envsubst.html @@ -3,7 +3,7 @@ - + git-sh-i18n--envsubst(1) +
+

SYNOPSIS

@@ -441,9 +609,11 @@ of Git. Don’t use it.

Part of the git(1) suite

+
+

diff --git a/git-sh-i18n.html b/git-sh-i18n.html index 2d3caa8e08..8913d2d774 100644 --- a/git-sh-i18n.html +++ b/git-sh-i18n.html @@ -3,7 +3,7 @@ - + git-sh-i18n(1) +
+

SYNOPSIS

@@ -461,9 +629,11 @@ eval_gettext

Part of the git(1) suite

+
+

diff --git a/git-sh-setup.html b/git-sh-setup.html index 18e961ee74..3a5d780a21 100644 --- a/git-sh-setup.html +++ b/git-sh-setup.html @@ -3,7 +3,7 @@ - + git-sh-setup(1) +
+

SYNOPSIS

@@ -528,9 +696,11 @@ get_author_ident_from_commit

Part of the git(1) suite

+
+

diff --git a/git-shell.html b/git-shell.html index 1d1097abdf..34dfcc1ef1 100644 --- a/git-shell.html +++ b/git-shell.html @@ -3,7 +3,7 @@ - + git-shell(1) +
+

SYNOPSIS

@@ -438,9 +606,11 @@ programs in it. The programs are executed with a cwd of $HOME, and

Part of the git(1) suite

+
+

diff --git a/git-shortlog.html b/git-shortlog.html index d5129cc02a..ef5d2a7375 100644 --- a/git-shortlog.html +++ b/git-shortlog.html @@ -3,7 +3,7 @@ - + git-shortlog(1) +
+

SYNOPSIS

@@ -588,9 +756,11 @@ the email address.

Part of the git(1) suite

+
+

diff --git a/git-show-branch.html b/git-show-branch.html index ca182d0611..17c7abd7a4 100644 --- a/git-show-branch.html +++ b/git-show-branch.html @@ -3,7 +3,7 @@ - + git-show-branch(1) +
+

SYNOPSIS

@@ -697,9 +865,11 @@ topologically related with each other.

Part of the git(1) suite

+
+

diff --git a/git-show-index.html b/git-show-index.html index 4bf9105de4..165f92b848 100644 --- a/git-show-index.html +++ b/git-show-index.html @@ -3,7 +3,7 @@ - + git-show-index(1) +
+

SYNOPSIS

@@ -431,9 +599,11 @@ offset and SHA1 of each object.

Part of the git(1) suite

+
+

diff --git a/git-show-ref.html b/git-show-ref.html index 3e60edc060..92c7eb7893 100644 --- a/git-show-ref.html +++ b/git-show-ref.html @@ -3,7 +3,7 @@ - + git-show-ref(1) +
+

SYNOPSIS

@@ -620,9 +788,11 @@ flag, so you can do

Part of the git(1) suite

+
+

diff --git a/git-show.html b/git-show.html index 4db79765b2..9995aa930b 100644 --- a/git-show.html +++ b/git-show.html @@ -3,7 +3,7 @@ - + git-show(1) +
+

SYNOPSIS

@@ -1109,9 +1277,11 @@ reversible operation.

Part of the git(1) suite

+
+

diff --git a/git-stage.html b/git-stage.html index 4e4309aec6..c20f1d4117 100644 --- a/git-stage.html +++ b/git-stage.html @@ -3,7 +3,7 @@ - + git-stage(1) +
+

SYNOPSIS

@@ -428,9 +596,11 @@ documentation of that command.

Part of the git(1) suite

+
+

diff --git a/git-stash.html b/git-stash.html index 02a5a295f8..154ebbea4d 100644 --- a/git-stash.html +++ b/git-stash.html @@ -3,7 +3,7 @@ - + git-stash(1) +
+

SYNOPSIS

@@ -717,9 +885,11 @@ xargs git log --merges --no-walk --grep=WIP

Part of the git(1) suite

+
+

diff --git a/git-status.html b/git-status.html index d3b263423b..eba951806b 100644 --- a/git-status.html +++ b/git-status.html @@ -3,7 +3,7 @@ - + git-status(1) +
+

SYNOPSIS

@@ -688,9 +856,11 @@ shown (see --summary-limit option of git-submodule( +
+

diff --git a/git-stripspace.html b/git-stripspace.html index 9222f1e0db..3133640de7 100644 --- a/git-stripspace.html +++ b/git-stripspace.html @@ -3,7 +3,7 @@ - + git-stripspace(1) +
+

SYNOPSIS

@@ -451,9 +619,11 @@ git-stripspace(1) Manual Page

Part of the git(1) suite

+
+

diff --git a/git-submodule.html b/git-submodule.html index 9fa9845166..758fcc48d1 100644 --- a/git-submodule.html +++ b/git-submodule.html @@ -3,7 +3,7 @@ - + git-submodule(1) +
+

SYNOPSIS

@@ -789,9 +957,11 @@ for details.

Part of the git(1) suite

+
+

diff --git a/git-svn.html b/git-svn.html index 1af80eb4b1..058b07a3e5 100644 --- a/git-svn.html +++ b/git-svn.html @@ -3,7 +3,7 @@ - + git-svn(1) +
+

SYNOPSIS

@@ -674,6 +842,29 @@ Skip "branches" and "tags" of first level directories affecting the working tree; and the rebase command will be able to update the working tree with the latest changes.

+
+
+--preserve-empty-dirs +
+
+

+ Create a placeholder file in the local Git repository for each + empty directory fetched from Subversion. This includes directories + that become empty by removing all entries in the Subversion + repository (but not the directory itself). The placeholder files + are also tracked and removed when no longer necessary. +

+
+
+--placeholder-filename=<filename> +
+
+

+ Set the name of placeholder files created by --preserve-empty-dirs. + Default: ".gitignore" +

+
+
rebase @@ -760,9 +951,18 @@ discouraged.

Add the given merge information during the dcommit (e.g. --mergeinfo="/branches/foo:1-10"). All svn server versions can store this information (as a property), and svn clients starting from - version 1.5 can make use of it. git svn currently does not use it - and does not set it automatically. + version 1.5 can make use of it. To specify merge information from multiple + branches, use a single space character between the branches + (--mergeinfo="/branches/foo:1-10 /branches/bar:3,5-6,8")

+
+
config key: svn.pushmergeinfo
+
+
+

This option will cause git-svn to attempt to automatically populate the +svn:mergeinfo property in the SVN repository when possible. Currently, this can +only be done when dcommitting non-fast-forward merges where all parents but the +first have already been pushed into SVN.

@@ -1787,9 +1987,11 @@ reset) branches-maxRev and/or tags-maxRev as appropriate.

Part of the git(1) suite

+
+

diff --git a/git-svn.txt b/git-svn.txt index ed5eca1fce..08cad6d2b6 100644 --- a/git-svn.txt +++ b/git-svn.txt @@ -157,6 +157,17 @@ Skip "branches" and "tags" of first level directories;; affecting the working tree; and the 'rebase' command will be able to update the working tree with the latest changes. +--preserve-empty-dirs;; + Create a placeholder file in the local Git repository for each + empty directory fetched from Subversion. This includes directories + that become empty by removing all entries in the Subversion + repository (but not the directory itself). The placeholder files + are also tracked and removed when no longer necessary. + +--placeholder-filename=;; + Set the name of placeholder files created by --preserve-empty-dirs. + Default: ".gitignore" + 'rebase':: This fetches revisions from the SVN parent of the current HEAD and rebases the current (uncommitted to SVN) work against it. @@ -211,8 +222,17 @@ discouraged. Add the given merge information during the dcommit (e.g. `--mergeinfo="/branches/foo:1-10"`). All svn server versions can store this information (as a property), and svn clients starting from - version 1.5 can make use of it. 'git svn' currently does not use it - and does not set it automatically. + version 1.5 can make use of it. To specify merge information from multiple + branches, use a single space character between the branches + (`--mergeinfo="/branches/foo:1-10 /branches/bar:3,5-6,8"`) ++ +[verse] +config key: svn.pushmergeinfo ++ +This option will cause git-svn to attempt to automatically populate the +svn:mergeinfo property in the SVN repository when possible. Currently, this can +only be done when dcommitting non-fast-forward merges where all parents but the +first have already been pushed into SVN. 'branch':: Create a branch in the SVN repository. diff --git a/git-symbolic-ref.html b/git-symbolic-ref.html index b3ae5e1d57..14dd4e7f9c 100644 --- a/git-symbolic-ref.html +++ b/git-symbolic-ref.html @@ -3,7 +3,7 @@ - + git-symbolic-ref(1) +
+

SYNOPSIS

@@ -478,9 +646,11 @@ name is not a symbolic ref, or 128 if another error occurs.

Part of the git(1) suite

+
+

diff --git a/git-tag.html b/git-tag.html index 4717ec7e6b..b24af60033 100644 --- a/git-tag.html +++ b/git-tag.html @@ -3,7 +3,7 @@ - + git-tag(1) +
+

SYNOPSIS

@@ -762,9 +930,11 @@ ISO 8601

Part of the git(1) suite

+
+

diff --git a/git-tar-tree.html b/git-tar-tree.html index 3c814ad28e..83b5db6965 100644 --- a/git-tar-tree.html +++ b/git-tar-tree.html @@ -3,7 +3,7 @@ - + git-tar-tree(1) +
+

SYNOPSIS

@@ -534,9 +702,11 @@ tar.umask

Part of the git(1) suite

+
+

diff --git a/git-tools.html b/git-tools.html index 24edbb3132..50bbbb9689 100644 --- a/git-tools.html +++ b/git-tools.html @@ -3,7 +3,7 @@ - + A short git tools survey + +

Introduction

Apart from git contrib/ area there are some others third-party tools @@ -561,9 +729,11 @@ tweaking to work on XEmacs.

+
+

diff --git a/git-unpack-file.html b/git-unpack-file.html index ce95079e12..25a27fa504 100644 --- a/git-unpack-file.html +++ b/git-unpack-file.html @@ -3,7 +3,7 @@ - + git-unpack-file(1) +
+

SYNOPSIS

@@ -442,9 +610,11 @@ returns the name of the temporary file in the following format:

Part of the git(1) suite

+
+

diff --git a/git-unpack-objects.html b/git-unpack-objects.html index b3b2eb432d..21513b7eb6 100644 --- a/git-unpack-objects.html +++ b/git-unpack-objects.html @@ -3,7 +3,7 @@ - + git-unpack-objects(1) +
+

SYNOPSIS

@@ -476,9 +644,11 @@ new packs and replace existing ones.

Part of the git(1) suite

+
+

diff --git a/git-update-index.html b/git-update-index.html index fc01ee4878..456b7031c1 100644 --- a/git-update-index.html +++ b/git-update-index.html @@ -3,7 +3,7 @@ - + git-update-index(1) +
+

SYNOPSIS

@@ -923,9 +1091,11 @@ ctime for marking files processed) (see git-config(1)< +
+

diff --git a/git-update-ref.html b/git-update-ref.html index 3b1afbb1d4..b73e285974 100644 --- a/git-update-ref.html +++ b/git-update-ref.html @@ -3,7 +3,7 @@ - + git-update-ref(1) +
+

SYNOPSIS

@@ -500,9 +668,11 @@ or does not have committer information available.

Part of the git(1) suite

+
+

diff --git a/git-update-server-info.html b/git-update-server-info.html index 7140a1435f..3349f452a5 100644 --- a/git-update-server-info.html +++ b/git-update-server-info.html @@ -3,7 +3,7 @@ - + git-update-server-info(1) +
+

SYNOPSIS

@@ -465,9 +633,11 @@ info/refs

Part of the git(1) suite

+
+

diff --git a/git-upload-archive.html b/git-upload-archive.html index cdf7f002d3..88ec5e1fe3 100644 --- a/git-upload-archive.html +++ b/git-upload-archive.html @@ -3,7 +3,7 @@ - + git-upload-archive(1) +
+

SYNOPSIS

@@ -444,9 +612,11 @@ is meant to be used to get an archive from a remote repository.

Part of the git(1) suite

+
+

diff --git a/git-upload-pack.html b/git-upload-pack.html index a7d7b897f4..7fb9df3b7c 100644 --- a/git-upload-pack.html +++ b/git-upload-pack.html @@ -3,7 +3,7 @@ - + git-upload-pack(1) +
+

SYNOPSIS

@@ -465,9 +633,11 @@ repository. For push operations, see git send-pack.

Part of the git(1) suite

+
+

diff --git a/git-var.html b/git-var.html index 3a81afec66..d55f09c661 100644 --- a/git-var.html +++ b/git-var.html @@ -3,7 +3,7 @@ - + git-var(1) +
+

SYNOPSIS

@@ -531,9 +699,11 @@ Your sysadmin must hate you!

Part of the git(1) suite

+
+

diff --git a/git-verify-pack.html b/git-verify-pack.html index 7992393d77..8e68b3d5d2 100644 --- a/git-verify-pack.html +++ b/git-verify-pack.html @@ -3,7 +3,7 @@ - + git-verify-pack(1) +
+

SYNOPSIS

@@ -488,9 +656,11 @@ corresponding pack file.

Part of the git(1) suite

+
+

diff --git a/git-verify-tag.html b/git-verify-tag.html index b0a9cde5a1..387098eb2e 100644 --- a/git-verify-tag.html +++ b/git-verify-tag.html @@ -3,7 +3,7 @@ - + git-verify-tag(1) +
+

SYNOPSIS

@@ -451,9 +619,11 @@ git-verify-tag(1) Manual Page

Part of the git(1) suite

+
+

diff --git a/git-web--browse.html b/git-web--browse.html index 277084d028..651a445b99 100644 --- a/git-web--browse.html +++ b/git-web--browse.html @@ -3,7 +3,7 @@ - + git-web--browse(1) +
+

SYNOPSIS

@@ -596,9 +764,11 @@ See git-config(1) for more information about this.

Part of the git(1) suite

+
+

diff --git a/git-whatchanged.html b/git-whatchanged.html index 8e5cfd1ec1..d2065bed77 100644 --- a/git-whatchanged.html +++ b/git-whatchanged.html @@ -3,7 +3,7 @@ - + git-whatchanged(1) +
+

SYNOPSIS

@@ -1040,9 +1208,11 @@ $ git log -2 --pretty=%h 4da45bef

Part of the git(1) suite

+
+

diff --git a/git-write-tree.html b/git-write-tree.html index ced247d0fd..6d2362ab1a 100644 --- a/git-write-tree.html +++ b/git-write-tree.html @@ -3,7 +3,7 @@ - + git-write-tree(1) +
+

SYNOPSIS

@@ -459,9 +627,11 @@ now, you need to have done a git update-index phase before you did the

Part of the git(1) suite

+
+

diff --git a/git.html b/git.html index 8d614c8750..a964c35dc0 100644 --- a/git.html +++ b/git.html @@ -3,7 +3,7 @@ - + git(1) +
+

SYNOPSIS

@@ -2226,9 +2394,11 @@ subscribed to the list to send a message there.

Part of the git(1) suite

+
+

diff --git a/git.txt b/git.txt index d08a8bb4f2..4ae21a3cc7 100644 --- a/git.txt +++ b/git.txt @@ -44,10 +44,12 @@ unreleased) version of git, that is available from 'master' branch of the `git.git` repository. Documentation for older releases are available here: -* link:v1.7.6.1/git.html[documentation for release 1.7.6.1] +* link:v1.7.6.3/git.html[documentation for release 1.7.6.3] * release notes for - link:RelNotes/1.7.6.1.txt[1.7.6.1]. + link:RelNotes/1.7.6.3.txt[1.7.6.3], + link:RelNotes/1.7.6.2.txt[1.7.6.2], + link:RelNotes/1.7.6.1.txt[1.7.6.1], link:RelNotes/1.7.6.txt[1.7.6]. * link:v1.7.5.4/git.html[documentation for release 1.7.5.4] diff --git a/gitattributes.html b/gitattributes.html index 51294bb750..2ef690bdf3 100644 --- a/gitattributes.html +++ b/gitattributes.html @@ -3,7 +3,7 @@ - + gitattributes(5) +
+

SYNOPSIS

$GIT_DIR/info/attributes, .gitattributes

@@ -1403,9 +1571,11 @@ frotz unspecified

Part of the git(1) suite

+
+

diff --git a/gitcli.html b/gitcli.html index a25f73361e..b7ffc480a2 100644 --- a/gitcli.html +++ b/gitcli.html @@ -3,7 +3,7 @@ - + gitcli(7) +
+

SYNOPSIS

gitcli

@@ -602,9 +770,11 @@ information.

Part of the git(1) suite

+
+

diff --git a/gitcore-tutorial.html b/gitcore-tutorial.html index 119b18f09d..ec665cad56 100644 --- a/gitcore-tutorial.html +++ b/gitcore-tutorial.html @@ -3,7 +3,7 @@ - + gitcore-tutorial(7) +
+

SYNOPSIS

git *

@@ -2139,9 +2307,11 @@ to follow, not easier.

Part of the git(1) suite.

+
+

diff --git a/gitcvs-migration.html b/gitcvs-migration.html index 6b5c574fb5..3735b24670 100644 --- a/gitcvs-migration.html +++ b/gitcvs-migration.html @@ -3,7 +3,7 @@ - + gitcvs-migration(7) +
+

SYNOPSIS

@@ -589,9 +757,11 @@ repositories without the need for a central maintainer.

Part of the git(1) suite.

+
+

diff --git a/gitdiffcore.html b/gitdiffcore.html index 01f4e0513f..f317ae4e9b 100644 --- a/gitdiffcore.html +++ b/gitdiffcore.html @@ -3,7 +3,7 @@ - + gitdiffcore(7) +
+

SYNOPSIS

@@ -697,9 +865,11 @@ t

Part of the git(1) suite.

+
+

diff --git a/gitglossary.html b/gitglossary.html index 46bafec5f0..f1d4d52aa7 100644 --- a/gitglossary.html +++ b/gitglossary.html @@ -3,7 +3,7 @@ - + gitglossary(7) +
+

SYNOPSIS

*

@@ -1329,9 +1497,11 @@ should not be combined with other pathspec.

Part of the git(1) suite.

+
+

diff --git a/githooks.html b/githooks.html index 87964697fa..f352183b38 100644 --- a/githooks.html +++ b/githooks.html @@ -3,7 +3,7 @@ - + githooks(5) +
+

SYNOPSIS

$GIT_DIR/hooks/*

@@ -691,9 +859,11 @@ processed by rebase.

Part of the git(1) suite

+
+

diff --git a/gitignore.html b/gitignore.html index 3836696d9c..674889f0c7 100644 --- a/gitignore.html +++ b/gitignore.html @@ -3,7 +3,7 @@ - + gitignore(5) +
+

SYNOPSIS

$GIT_DIR/info/exclude, .gitignore

@@ -595,9 +763,11 @@ use git update-index --assume-unchanged.

Part of the git(1) suite

+
+

diff --git a/gitk.html b/gitk.html index e132efd7e6..c901c504e6 100644 --- a/gitk.html +++ b/gitk.html @@ -3,7 +3,7 @@ - + gitk(1) +
+

SYNOPSIS

@@ -600,9 +768,11 @@ such as display options, font, and colors.

Part of the git(1) suite

+
+

diff --git a/gitmodules.html b/gitmodules.html index 5763a27a6a..497cc62a37 100644 --- a/gitmodules.html +++ b/gitmodules.html @@ -3,7 +3,7 @@ - + gitmodules(5) +
+

SYNOPSIS

$GIT_WORK_DIR/.gitmodules

@@ -525,9 +693,11 @@ submodules an url is specified which can be used for cloning the submodules.

Part of the git(1) suite

+
+

diff --git a/gitnamespaces.html b/gitnamespaces.html index 1a71c77cdd..ed9db5d7e5 100644 --- a/gitnamespaces.html +++ b/gitnamespaces.html @@ -3,7 +3,7 @@ - + gitnamespaces(7) +
+

DESCRIPTION

Git supports dividing the refs of a single repository into multiple @@ -480,9 +648,11 @@ if everyone who may read one namespace may also read everything in every other namespace (for instance, if everyone in an organization has read permission to every repository).

+
+

diff --git a/gitrepository-layout.html b/gitrepository-layout.html index 4752a8c5b9..59da8a3645 100644 --- a/gitrepository-layout.html +++ b/gitrepository-layout.html @@ -3,7 +3,7 @@ - + gitrepository-layout(5) +
+

SYNOPSIS

$GIT_DIR/*

@@ -745,9 +913,11 @@ shallow

Part of the git(1) suite.

+
+

diff --git a/gitrevisions.html b/gitrevisions.html index fb6ffdedb8..7769c71022 100644 --- a/gitrevisions.html +++ b/gitrevisions.html @@ -3,7 +3,7 @@ - + gitrevisions(7) +
+

SYNOPSIS

gitrevisions

@@ -761,9 +929,11 @@ F^! D G H D F

Part of the git(1) suite

+
+

diff --git a/gittutorial-2.html b/gittutorial-2.html index c5590686f7..aa8567504d 100644 --- a/gittutorial-2.html +++ b/gittutorial-2.html @@ -3,7 +3,7 @@ - + gittutorial-2(7) +
+

SYNOPSIS

@@ -819,9 +987,11 @@ example, creating a new commit.

Part of the git(1) suite.

+
+

diff --git a/gittutorial.html b/gittutorial.html index 26e9d619ff..89236c38c0 100644 --- a/gittutorial.html +++ b/gittutorial.html @@ -3,7 +3,7 @@ - + gittutorial(7) +
+

SYNOPSIS

@@ -1011,9 +1179,11 @@ digressions that may be interesting at this point are:

Part of the git(1) suite.

+
+

diff --git a/gitworkflows.html b/gitworkflows.html index 950589c39f..7a6896de43 100644 --- a/gitworkflows.html +++ b/gitworkflows.html @@ -3,7 +3,7 @@ - + gitworkflows(7) +
+

SYNOPSIS

@@ -860,9 +1028,11 @@ other options.

Part of the git(1) suite.

+
+

diff --git a/howto-index.html b/howto-index.html index b4495e36fe..558aa2b72c 100644 --- a/howto-index.html +++ b/howto-index.html @@ -3,7 +3,7 @@ - + GIT Howto Index + +

Here is a collection of mailing list postings made by various @@ -492,9 +660,11 @@ into which branch and who can make a tag.

strategy.

+
+

diff --git a/howto/maintain-git.txt b/howto/maintain-git.txt index d527b30770..8823a37067 100644 --- a/howto/maintain-git.txt +++ b/howto/maintain-git.txt @@ -176,7 +176,7 @@ by doing the following: - Update "What's cooking" message to review the updates to existing topics, newly added topics and graduated topics. - This step is helped with Meta/UWC script (where Meta/ contains + This step is helped with Meta/cook script (where Meta/ contains a checkout of the 'todo' branch). - Merge topics to 'next'. For each branch whose tip is not @@ -197,10 +197,9 @@ by doing the following: - Nothing is next-worthy; do not do anything. - - Rebase topics that do not have any commit in next yet. This - step is optional but sometimes is worth doing when an old - series that is not in next can take advantage of low-level - framework change that is merged to 'master' already. + - [** OBSOLETE **] Optionally rebase topics that do not have any commit + in next yet, when they can take advantage of low-level framework + change that is merged to 'master' already. $ git rebase master ai/topic @@ -209,7 +208,7 @@ by doing the following: pre-rebase hook to make sure that topics that are already in 'next' are not rebased beyond the merged commit. - - Rebuild "pu" to merge the tips of topics not in 'next'. + - [** OBSOLETE **] Rebuild "pu" to merge the tips of topics not in 'next'. $ git checkout pu $ git reset --hard next @@ -241,7 +240,7 @@ by doing the following: - Fetch html and man branches back from k.org, and push four integration branches and the two documentation branches to - repo.or.cz + repo.or.cz and other mirrors. Some observations to be made. diff --git a/howto/revert-branch-rebase.html b/howto/revert-branch-rebase.html index 7b348bc422..4841cfb625 100644 --- a/howto/revert-branch-rebase.html +++ b/howto/revert-branch-rebase.html @@ -3,7 +3,7 @@ - + Reverting an existing commit + +

One of the changes I pulled into the master branch turns out to @@ -551,9 +719,11 @@ Committed merge 7fb9b7262a1d1e0a47bbfdcbbcf50ce0635d3f8f

+
+

diff --git a/howto/using-merge-subtree.html b/howto/using-merge-subtree.html index f300125067..97ec363f83 100644 --- a/howto/using-merge-subtree.html +++ b/howto/using-merge-subtree.html @@ -3,7 +3,7 @@ - + How to use the subtree merge strategy + +

There are situations where you want to include contents in your project @@ -488,9 +656,11 @@ Please note that if the other project merges from you, then it will

+
+

diff --git a/technical/api-allocation-growing.html b/technical/api-allocation-growing.html index 43e45d97e6..b33f564a56 100644 --- a/technical/api-allocation-growing.html +++ b/technical/api-allocation-growing.html @@ -3,7 +3,7 @@ - + allocation growing API + +

Dynamically growing an array using realloc() is error prone and boring.

@@ -429,9 +597,11 @@ ary[nr++] = value you like;

You are responsible for updating the nr variable.

+
+

diff --git a/technical/api-builtin.html b/technical/api-builtin.html index 2781da9015..6754dc3fcd 100644 --- a/technical/api-builtin.html +++ b/technical/api-builtin.html @@ -3,7 +3,7 @@ - + builtin API + +

Adding a new built-in

There are 4 things to do to add a built-in command implementation to @@ -493,9 +661,11 @@ to a pathname relative to the top of the work tree.

The return value from cmd_foo() becomes the exit status of the command.

+
+

diff --git a/technical/api-decorate.html b/technical/api-decorate.html index fc5ff103b2..4fff4e9124 100644 --- a/technical/api-decorate.html +++ b/technical/api-decorate.html @@ -3,7 +3,7 @@ - + decorate API + +

Talk about <decorate.h>

(Linus)

+
+

diff --git a/technical/api-diff.html b/technical/api-diff.html index 41b0f9f561..4713070785 100644 --- a/technical/api-diff.html +++ b/technical/api-diff.html @@ -3,7 +3,7 @@ - + diff API + +

The diff API is for programs that compare two sets of files (e.g. two @@ -705,9 +873,11 @@ RECURSIVE, TREE_IN_RECURSIVE

(JC)

+
+

diff --git a/technical/api-directory-listing.html b/technical/api-directory-listing.html index cf6c25f583..0ded726c20 100644 --- a/technical/api-directory-listing.html +++ b/technical/api-directory-listing.html @@ -3,7 +3,7 @@ - + directory listing API + +

The directory listing API is used to enumerate paths in the work tree, @@ -518,9 +686,11 @@ Use dir.entries[].

(JC)

+
+

diff --git a/technical/api-gitattributes.html b/technical/api-gitattributes.html index 032011d4f6..1acb5a5124 100644 --- a/technical/api-gitattributes.html +++ b/technical/api-gitattributes.html @@ -3,7 +3,7 @@ - + gitattributes API + +

gitattributes mechanism gives a uniform way to associate various @@ -567,9 +735,11 @@ Free the git_array_check array.

+
+

diff --git a/technical/api-grep.html b/technical/api-grep.html index 201bd2ecef..b3c6a30483 100644 --- a/technical/api-grep.html +++ b/technical/api-grep.html @@ -3,7 +3,7 @@ - + grep API + +

Talk about <grep.h>, things like:

@@ -399,9 +567,11 @@ grep_buffer()

(JC)

+
+

diff --git a/technical/api-hash.html b/technical/api-hash.html index 6a220f3113..43ef8a7ee6 100644 --- a/technical/api-hash.html +++ b/technical/api-hash.html @@ -3,7 +3,7 @@ - + hash API + +

The hash API is a collection of simple hash table functions. Users are expected @@ -471,9 +639,11 @@ to implement their own hashing.

+
+

diff --git a/technical/api-history-graph.html b/technical/api-history-graph.html index c3e7aade92..28ff08ec4f 100644 --- a/technical/api-history-graph.html +++ b/technical/api-history-graph.html @@ -3,7 +3,7 @@ - + history graph API + +

The graph API is used to draw a text-based representation of the commit @@ -616,9 +784,11 @@ outputting that information, if desired.

| | | | *
+
+

diff --git a/technical/api-in-core-index.html b/technical/api-in-core-index.html index 07fd21167e..e84fc2e470 100644 --- a/technical/api-in-core-index.html +++ b/technical/api-in-core-index.html @@ -3,7 +3,7 @@ - + in-core index API + +

Talk about <read-cache.c> and <cache-tree.c>, things like:

@@ -460,9 +628,11 @@ cache_tree_update()

(JC, Linus)

+
+

diff --git a/technical/api-index.html b/technical/api-index.html index ca293aba5c..702fa6fc34 100644 --- a/technical/api-index.html +++ b/technical/api-index.html @@ -3,7 +3,7 @@ - + GIT API Documents + +

GIT has grown a set of internal API over time. This collection @@ -520,9 +688,11 @@ documents them.

2007-11-24

+
+

diff --git a/technical/api-lockfile.html b/technical/api-lockfile.html index 62b7981141..f805e4ba2c 100644 --- a/technical/api-lockfile.html +++ b/technical/api-lockfile.html @@ -3,7 +3,7 @@ - + lockfile API + +

The lockfile API serves two purposes:

@@ -484,9 +652,11 @@ descriptor for completely different purpose, and then call commit_lock_file() or rollback_lock_file(), they may close that unrelated file descriptor.

+
+

diff --git a/technical/api-merge.html b/technical/api-merge.html index 4c3ec10cb1..de3829f2a8 100644 --- a/technical/api-merge.html +++ b/technical/api-merge.html @@ -3,7 +3,7 @@ - + merge API + +

The merge API helps a program to reconcile two competing sets of @@ -569,9 +737,11 @@ merge options

(Daniel, Miklos, Stephan, JC)

+
+

diff --git a/technical/api-object-access.html b/technical/api-object-access.html index a2e483b301..4036e522fd 100644 --- a/technical/api-object-access.html +++ b/technical/api-object-access.html @@ -3,7 +3,7 @@ - + object access API + +

Talk about <sha1_file.c> and <object.h> family, things like

@@ -434,9 +602,11 @@ Use of object flags

(JC, Shawn, Daniel, Dscho, Linus)

+
+

diff --git a/technical/api-parse-options.html b/technical/api-parse-options.html index 49e8902666..6d89568b25 100644 --- a/technical/api-parse-options.html +++ b/technical/api-parse-options.html @@ -3,7 +3,7 @@ - + parse-options API + +

The parse-options API is used to parse and massage options in git @@ -845,9 +1013,11 @@ in parse-options.h itself.

builtin-rm.c for real-world examples.

+
+

diff --git a/technical/api-quote.html b/technical/api-quote.html index dc715b0ba9..fa1891c69c 100644 --- a/technical/api-quote.html +++ b/technical/api-quote.html @@ -3,7 +3,7 @@ - + quote API + +

Talk about <quote.h>, things like

@@ -409,9 +577,11 @@ quoting for foreign languages

(JC)

+
+

diff --git a/technical/api-ref-iteration.html b/technical/api-ref-iteration.html index 56389e503f..ad66a4421d 100644 --- a/technical/api-ref-iteration.html +++ b/technical/api-ref-iteration.html @@ -3,7 +3,7 @@ - + ref iteration API + +

Iteration of refs is done by using an iterate function which will call a @@ -496,9 +664,11 @@ will be available the same way as the superprojects objects.

printf("%s", output.buf);
+
+

diff --git a/technical/api-remote.html b/technical/api-remote.html index f709fa640d..61de24865a 100644 --- a/technical/api-remote.html +++ b/technical/api-remote.html @@ -3,7 +3,7 @@ - + Remotes configuration API + +

The API in remote.h gives access to the configuration related to @@ -567,9 +735,11 @@ configuration given.

process of interacting with remotes.

(Daniel Barkalow)

+
+

diff --git a/technical/api-revision-walking.html b/technical/api-revision-walking.html index 7f0aed282e..f77fd11724 100644 --- a/technical/api-revision-walking.html +++ b/technical/api-revision-walking.html @@ -3,7 +3,7 @@ - + revision walking API + +

The revision walking API offers functions to build a list of revisions @@ -488,9 +656,11 @@ remaining functions;

(Linus, JC, Dscho)

+
+

diff --git a/technical/api-run-command.html b/technical/api-run-command.html index a378a84ce4..6d5a2b7b18 100644 --- a/technical/api-run-command.html +++ b/technical/api-run-command.html @@ -3,7 +3,7 @@ - + run-command API + +

The run-command API offers a versatile tool to run sub-processes with @@ -795,9 +963,11 @@ It must not change the program’s state that the caller of the

+
+

diff --git a/technical/api-setup.html b/technical/api-setup.html index 1cbc82781a..47105d52f2 100644 --- a/technical/api-setup.html +++ b/technical/api-setup.html @@ -3,7 +3,7 @@ - + setup API + +

Talk about

@@ -424,9 +592,11 @@ get_pathspec()

(Dscho)

+
+

diff --git a/technical/api-sigchain.html b/technical/api-sigchain.html index b0b5d5eaae..5957c066ba 100644 --- a/technical/api-sigchain.html +++ b/technical/api-sigchain.html @@ -3,7 +3,7 @@ - + sigchain API + +

Code often wants to set a signal handler to clean up temporary files or @@ -433,9 +601,11 @@ convenience, sigchain_push_common will push the handler onto the stack for many common signals.

+
+

diff --git a/technical/api-strbuf.html b/technical/api-strbuf.html index cd63f6a661..5f46aa03b4 100644 --- a/technical/api-strbuf.html +++ b/technical/api-strbuf.html @@ -3,7 +3,7 @@ - + strbuf API + +

strbuf’s are meant to be used with all the usual C string and memory @@ -845,9 +1013,11 @@ same behaviour as well.

+
+

diff --git a/technical/api-string-list.html b/technical/api-string-list.html index 63060f02cc..7e4be9bd3e 100644 --- a/technical/api-string-list.html +++ b/technical/api-string-list.html @@ -3,7 +3,7 @@ - + string-list API + +

The string_list API offers a data structure and functions to handle sorted @@ -430,6 +598,12 @@ Can sort an unsorted list using sort_string_list.

  • +Can remove individual items of an unsorted list using + unsorted_string_list_delete_item. +

    +
  • +
  • +

    Finally it should free the list using string_list_clear.

  • @@ -569,6 +743,17 @@ Functions for unsorted lists only

    The above two functions need to look through all items, as opposed to their counterpart for sorted lists, which performs a binary search.

    +
    +unsorted_string_list_delete_item +
    +
    +

    + Remove an item from a string_list. The string pointer of the items + will be freed in case the strdup_strings member of the string_list + is set. The third parameter controls if the util pointer of the + items should be freed or not. +

    +
    @@ -617,9 +802,11 @@ Setting the strdup_strings member to 1 will strdup() the strings
    +
    +

    diff --git a/technical/api-string-list.txt b/technical/api-string-list.txt index 3f575bdcff..ce24eb96f5 100644 --- a/technical/api-string-list.txt +++ b/technical/api-string-list.txt @@ -29,6 +29,9 @@ member (you need this if you add things later) and you should set the . Can sort an unsorted list using `sort_string_list`. +. Can remove individual items of an unsorted list using + `unsorted_string_list_delete_item`. + . Finally it should free the list using `string_list_clear`. Example: @@ -112,6 +115,13 @@ write `string_list_insert(...)->util = ...;`. The above two functions need to look through all items, as opposed to their counterpart for sorted lists, which performs a binary search. +`unsorted_string_list_delete_item`:: + + Remove an item from a string_list. The `string` pointer of the items + will be freed in case the `strdup_strings` member of the string_list + is set. The third parameter controls if the `util` pointer of the + items should be freed or not. + Data structures --------------- diff --git a/technical/api-tree-walking.html b/technical/api-tree-walking.html index 44b19cbe2c..a1b5d6568c 100644 --- a/technical/api-tree-walking.html +++ b/technical/api-tree-walking.html @@ -3,7 +3,7 @@ - + tree walking API + +

    The tree walking API is used to traverse and inspect trees.

    @@ -651,9 +819,11 @@ same in the next callback invocation.

    Written by Junio C Hamano <gitster@pobox.com> and Linus Torvalds <torvalds@linux-foundation.org>

    +
    +

    diff --git a/technical/api-xdiff-interface.html b/technical/api-xdiff-interface.html index 082e68ccfb..ba70e5a3dd 100644 --- a/technical/api-xdiff-interface.html +++ b/technical/api-xdiff-interface.html @@ -3,7 +3,7 @@ - + xdiff interface API + +

    Talk about our calling convention to xdiff library, including @@ -393,9 +561,11 @@ xdiff_emit_consume_fn.

    (Dscho, JC)

    +
    +

    diff --git a/user-manual.html b/user-manual.html index d2dfd35d33..d21fd6740d 100644 --- a/user-manual.html +++ b/user-manual.html @@ -1,5 +1,5 @@ -Git User’s Manual (for version 1.5.3 or newer)

    Git User’s Manual (for version 1.5.3 or newer)


    Table of Contents

    1. Repositories and Branches
    How to get a git repository
    How to check out a different version of a project
    Understanding History: Commits
    Understanding history: commits, parents, and reachability
    Understanding history: History diagrams
    Understanding history: What is a branch?
    Manipulating branches
    Examining an old version without creating a new branch
    Examining branches from a remote repository
    Naming branches, tags, and other references
    Updating a repository with git fetch
    Fetching branches from other repositories
    2. Exploring git history
    How to use bisect to find a regression
    Naming commits
    Creating tags
    Browsing revisions
    Generating diffs
    Viewing old file versions
    Examples
    Counting the number of commits on a branch
    Check whether two branches point at the same history
    Find first tagged version including a given fix
    Showing commits unique to a given branch
    Creating a changelog and tarball for a software release
    Finding commits referencing a file with given content
    3. Developing with git
    Telling git your name
    Creating a new repository
    How to make a commit
    Creating good commit messages
    Ignoring files
    How to merge
    Resolving a merge
    Getting conflict-resolution help during a merge
    Undoing a merge
    Fast-forward merges
    Fixing mistakes
    Fixing a mistake with a new commit
    Fixing a mistake by rewriting history
    Checking out an old version of a file
    Temporarily setting aside work in progress
    Ensuring good performance
    Ensuring reliability
    Checking the repository for corruption
    Recovering lost changes
    4. Sharing development with others
    Getting updates with git pull
    Submitting patches to a project
    Importing patches to a project
    Public git repositories
    Setting up a public repository
    Exporting a git repository via the git protocol
    Exporting a git repository via http
    Pushing changes to a public repository
    What to do when a push fails
    Setting up a shared repository
    Allowing web browsing of a repository
    Examples
    Maintaining topic branches for a Linux subsystem maintainer
    5. Rewriting history and maintaining patch series
    Creating the perfect patch series
    Keeping a patch series up to date using git rebase
    Rewriting a single commit
    Reordering or selecting from a patch series
    Other tools
    Problems with rewriting history
    Why bisecting merge commits can be harder than bisecting linear history
    6. Advanced branch management
    Fetching individual branches
    git fetch and fast-forwards
    Forcing git fetch to do non-fast-forward updates
    Configuring remote-tracking branches
    7. Git concepts
    The Object Database
    Commit Object
    Tree Object
    Blob Object
    Trust
    Tag Object
    How git stores objects efficiently: pack files
    Dangling objects
    Recovering from repository corruption
    The index
    8. Submodules
    Pitfalls with submodules
    9. Low-level git operations
    Object access and manipulation
    The Workflow
    working directory → index
    index → object database
    object database → index
    index → working directory
    Tying it all together
    Examining the data
    Merging multiple trees
    Merging multiple trees, continued
    10. Hacking git
    Object storage format
    A birds-eye view of Git’s source code
    11. Git Glossary
    A. Git Quick Reference
    Creating a new repository
    Managing branches
    Exploring history
    Making changes
    Merging
    Sharing your changes
    Repository maintenance
    B. Notes and todo list for this manual

    Git is a fast distributed revision control system.

    This manual is designed to be readable by someone with basic UNIX +Git User’s Manual (for version 1.5.3 or newer)

    Git User’s Manual (for version 1.5.3 or newer)


    Table of Contents

    1. Repositories and Branches
    How to get a git repository
    How to check out a different version of a project
    Understanding History: Commits
    Understanding history: commits, parents, and reachability
    Understanding history: History diagrams
    Understanding history: What is a branch?
    Manipulating branches
    Examining an old version without creating a new branch
    Examining branches from a remote repository
    Naming branches, tags, and other references
    Updating a repository with git fetch
    Fetching branches from other repositories
    2. Exploring git history
    How to use bisect to find a regression
    Naming commits
    Creating tags
    Browsing revisions
    Generating diffs
    Viewing old file versions
    Examples
    Counting the number of commits on a branch
    Check whether two branches point at the same history
    Find first tagged version including a given fix
    Showing commits unique to a given branch
    Creating a changelog and tarball for a software release
    Finding commits referencing a file with given content
    3. Developing with git
    Telling git your name
    Creating a new repository
    How to make a commit
    Creating good commit messages
    Ignoring files
    How to merge
    Resolving a merge
    Getting conflict-resolution help during a merge
    Undoing a merge
    Fast-forward merges
    Fixing mistakes
    Fixing a mistake with a new commit
    Fixing a mistake by rewriting history
    Checking out an old version of a file
    Temporarily setting aside work in progress
    Ensuring good performance
    Ensuring reliability
    Checking the repository for corruption
    Recovering lost changes
    4. Sharing development with others
    Getting updates with git pull
    Submitting patches to a project
    Importing patches to a project
    Public git repositories
    Setting up a public repository
    Exporting a git repository via the git protocol
    Exporting a git repository via http
    Pushing changes to a public repository
    What to do when a push fails
    Setting up a shared repository
    Allowing web browsing of a repository
    Examples
    Maintaining topic branches for a Linux subsystem maintainer
    5. Rewriting history and maintaining patch series
    Creating the perfect patch series
    Keeping a patch series up to date using git rebase
    Rewriting a single commit
    Reordering or selecting from a patch series
    Other tools
    Problems with rewriting history
    Why bisecting merge commits can be harder than bisecting linear history
    6. Advanced branch management
    Fetching individual branches
    git fetch and fast-forwards
    Forcing git fetch to do non-fast-forward updates
    Configuring remote-tracking branches
    7. Git concepts
    The Object Database
    Commit Object
    Tree Object
    Blob Object
    Trust
    Tag Object
    How git stores objects efficiently: pack files
    Dangling objects
    Recovering from repository corruption
    The index
    8. Submodules
    Pitfalls with submodules
    9. Low-level git operations
    Object access and manipulation
    The Workflow
    working directory → index
    index → object database
    object database → index
    index → working directory
    Tying it all together
    Examining the data
    Merging multiple trees
    Merging multiple trees, continued
    10. Hacking git
    Object storage format
    A birds-eye view of Git’s source code
    11. Git Glossary
    A. Git Quick Reference
    Creating a new repository
    Managing branches
    Exploring history
    Making changes
    Merging
    Sharing your changes
    Repository maintenance
    B. Notes and todo list for this manual

    Git is a fast distributed revision control system.

    This manual is designed to be readable by someone with basic UNIX command-line skills, but no previous knowledge of git.

    Chapter 1, Repositories and Branches and Chapter 2, Exploring git history explain how to fetch and study a project using git—read these chapters to learn how to build and test a particular version of a software project, search for -- 2.11.4.GIT