Skip to content

Commit

Permalink
Sync with maint
Browse files Browse the repository at this point in the history
* maint:
  Start preparing for 1.8.4.3
  gitignore.txt: fix documentation of "**" patterns
  • Loading branch information
Junio C Hamano committed Nov 7, 2013
2 parents 6ba01ba + 486b65a commit 867b1c1
Show file tree
Hide file tree
Showing 2 changed files with 39 additions and 3 deletions.
36 changes: 36 additions & 0 deletions Documentation/RelNotes/1.8.4.3.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
Git v1.8.4.3 Release Notes
========================

Fixes since v1.8.4.2
--------------------

* "git rev-list --objects ^v1.0^ v1.0" gave v1.0 tag itself in the
output, but "git rev-list --objects v1.0^..v1.0" did not.

* The fall-back parsing of commit objects with broken author or
committer lines were less robust than ideal in picking up the
timestamps.

* Bash prompting code to deal with an SVN remote as an upstream
were coded in a way not supported by older Bash versions (3.x).

* "git checkout topic", when there is not yet a local "topic" branch
but there is a unique remote-tracking branch for a remote "topic"
branch, pretended as if "git checkout -t -b topic remote/$r/topic"
(for that unique remote $r) was run. This hack however was not
implemented for "git checkout topic --".

* Coloring around octopus merges in "log --graph" output was screwy.

* We did not generate HTML version of documentation to "git subtree"
in contrib/.

* The synopsis section of "git unpack-objects" documentation has been
clarified a bit.

* An ancient How-To on serving Git repositories on an HTTP server
lacked a warning that it has been mostly superseded with more
modern way.

Also contains a handful of trivial code clean-ups, documentation
updates, updates to the test suite, etc.
6 changes: 3 additions & 3 deletions Documentation/gitignore.txt
Original file line number Diff line number Diff line change
Expand Up @@ -113,12 +113,12 @@ full pathname may have special meaning:

- A leading "`**`" followed by a slash means match in all
directories. For example, "`**/foo`" matches file or directory
"`foo`" anywhere, the same as pattern "`foo`". "**/foo/bar"
"`foo`" anywhere, the same as pattern "`foo`". "`**/foo/bar`"
matches file or directory "`bar`" anywhere that is directly
under directory "`foo`".

- A trailing "/**" matches everything inside. For example,
"abc/**" matches all files inside directory "abc", relative
- A trailing "`/**`" matches everything inside. For example,
"`abc/**`" matches all files inside directory "`abc`", relative
to the location of the `.gitignore` file, with infinite depth.

- A slash followed by two consecutive asterisks then a slash
Expand Down

0 comments on commit 867b1c1

Please sign in to comment.