summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/RelNotes/1.8.4.txt20
-rw-r--r--Documentation/git-check-ref-format.txt2
-rw-r--r--Documentation/git-merge.txt4
-rw-r--r--Documentation/git-stash.txt12
-rw-r--r--Documentation/git.txt5
-rw-r--r--Documentation/revisions.txt3
6 files changed, 18 insertions, 28 deletions
diff --git a/Documentation/RelNotes/1.8.4.txt b/Documentation/RelNotes/1.8.4.txt
index b4f8737c5a..02f681b710 100644
--- a/Documentation/RelNotes/1.8.4.txt
+++ b/Documentation/RelNotes/1.8.4.txt
@@ -198,9 +198,6 @@ UI, Workflows & Features
response was to stash them and re-run). This introduced a corner
case breakage to "git am --abort" but it has been fixed.
- * Instead of typing four capital letters "HEAD", you can say "@" now,
- e.g. "git log @".
-
* "check-ignore" (new feature since 1.8.2) has been updated to work
more like "check-attr" over bidi-pipes.
@@ -242,6 +239,13 @@ UI, Workflows & Features
Performance, Internal Implementation, etc.
+ * On Cygwin, we used to use our own lstat(2) emulation that is
+ allegedly faster than the platform one in codepaths where some of
+ the information it returns did not matter, but it started to bite
+ us in a few codepaths where the trick it uses to cheat does show
+ breakages. This emulation has been removed and we use the native
+ lstat(2) emulation supplied by Cygwin now.
+
* The function attributes extensions are used to catch mistakes in
use of our own variadic functions that use NULL sentinel at the end
(i.e. like execl(3)) and format strings (i.e. like printf(3)).
@@ -263,7 +267,7 @@ Performance, Internal Implementation, etc.
been susceptible to lossage of refs under right conditions, which
has been tightened up.
- * We read loose and packed rerferences in two steps, but after
+ * We read loose and packed references in two steps, but after
deciding to read a loose ref but before actually opening it to read
it, another process racing with us can unlink it, which would cause
us to barf. The codepath has been updated to retry when such a
@@ -365,12 +369,6 @@ details).
the user to an unexpected place.
(merge 3bed291 rr/rebase-checkout-reflog later to maint).
- * "git stash save", when your local change turns a tracked file into
- a directory, has to remove files in that directory in order to
- revert your working tree to a pristine state. This will lose
- untracked files in such a directory, and the command now requires
- you to "--force" it.
-
* The configuration variable column.ui was poorly documented.
(merge 5e62cc1 rr/column-doc later to maint).
@@ -381,7 +379,7 @@ details).
* "git apply" parsed patches that add new files, generated by
programs other than Git, incorrectly. This is an old breakage in
- v1.7.11 and will need to be merged down to the maintanance tracks.
+ v1.7.11 and will need to be merged down to the maintenance tracks.
* Older cURL wanted piece of memory we call it with to be stable, but
we updated the auth material after handing it to a call.
diff --git a/Documentation/git-check-ref-format.txt b/Documentation/git-check-ref-format.txt
index fc02959ba4..a49be1bab4 100644
--- a/Documentation/git-check-ref-format.txt
+++ b/Documentation/git-check-ref-format.txt
@@ -54,8 +54,6 @@ Git imposes the following rules on how references are named:
. They cannot contain a sequence `@{`.
-. They cannot be the single character `@`.
-
. They cannot contain a `\`.
These rules make it easy for shell script based tools to parse
diff --git a/Documentation/git-merge.txt b/Documentation/git-merge.txt
index 8c7f2f66d8..a74c3713c6 100644
--- a/Documentation/git-merge.txt
+++ b/Documentation/git-merge.txt
@@ -186,11 +186,11 @@ In such a case, you can "unwrap" the tag yourself before feeding it
to `git merge`, or pass `--ff-only` when you do not have any work on
your own. e.g.
----
+----
git fetch origin
git merge v1.2.3^0
git merge --ff-only v1.2.3
----
+----
HOW CONFLICTS ARE PRESENTED
diff --git a/Documentation/git-stash.txt b/Documentation/git-stash.txt
index 7c8b648fbe..db7e803038 100644
--- a/Documentation/git-stash.txt
+++ b/Documentation/git-stash.txt
@@ -14,8 +14,7 @@ SYNOPSIS
'git stash' ( pop | apply ) [--index] [-q|--quiet] [<stash>]
'git stash' branch <branchname> [<stash>]
'git stash' [save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet]
- [-u|--include-untracked] [-a|--all] [-f|--force]
- [<message>]]
+ [-u|--include-untracked] [-a|--all] [<message>]]
'git stash' clear
'git stash' create [<message>]
'git stash' store [-m|--message <message>] [-q|--quiet] <commit>
@@ -45,7 +44,7 @@ is also possible).
OPTIONS
-------
-save [-p|--patch] [--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [-f|--force] [<message>]::
+save [-p|--patch] [--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [<message>]::
Save your local modifications to a new 'stash', and run `git reset
--hard` to revert them. The <message> part is optional and gives
@@ -72,13 +71,6 @@ linkgit:git-add[1] to learn how to operate the `--patch` mode.
+
The `--patch` option implies `--keep-index`. You can use
`--no-keep-index` to override this.
-+
-In some cases, saving a stash could mean irretrievably removing some
-data - if a directory with untracked files replaces a tracked file of
-the same name, the new untracked files are not saved (except in case
-of `--include-untracked`) but the original tracked file shall be restored.
-By default, `stash save` will abort in such a case; `--force` will allow
-it to remove the untracked files.
list [<options>]::
diff --git a/Documentation/git.txt b/Documentation/git.txt
index 3bdd56e8f4..dca11cc96e 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -43,6 +43,11 @@ unreleased) version of Git, that is available from 'master'
branch of the `git.git` repository.
Documentation for older releases are available here:
+* link:v1.8.4/git.html[documentation for release 1.8.4]
+
+* release notes for
+ link:RelNotes/1.8.4.txt[1.8.4].
+
* link:v1.8.3.4/git.html[documentation for release 1.8.3.4]
* release notes for
diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt
index 09896a37b1..d477b3f6bc 100644
--- a/Documentation/revisions.txt
+++ b/Documentation/revisions.txt
@@ -58,9 +58,6 @@ the '$GIT_DIR/refs' directory or from the '$GIT_DIR/packed-refs' file.
While the ref name encoding is unspecified, UTF-8 is preferred as
some output processing may assume ref names in UTF-8.
-'@'::
- '@' alone is a shortcut for 'HEAD'.
-
'<refname>@\{<date>\}', e.g. 'master@\{yesterday\}', 'HEAD@\{5 minutes ago\}'::
A ref followed by the suffix '@' with a date specification
enclosed in a brace