Skip to content

Commit bd3e186

Browse files
committed
Git 1.9-rc1
Signed-off-by: Junio C Hamano <[email protected]>
1 parent 8bba720 commit bd3e186

File tree

2 files changed

+47
-1
lines changed

2 files changed

+47
-1
lines changed

Documentation/RelNotes/1.9.txt

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -87,6 +87,8 @@ Foreign interfaces, subsystems and ports.
8787

8888
* The build procedure is aware of MirBSD now.
8989

90+
* Various "git p4", "git svn" and "gitk" updates.
91+
9092

9193
UI, Workflows & Features
9294

@@ -215,6 +217,50 @@ Unless otherwise noted, all the fixes since v1.8.5 in the maintenance
215217
track are contained in this release (see the maintenance releases' notes
216218
for details).
217219

220+
* The pathspec matching code, while comparing two trees (e.g. "git
221+
diff A B -- path1 path2") was too agrresive and failed to match
222+
some paths when multiple pathspecs were involved.
223+
(merge e4ddb05 as/tree-walk-fix-aggressive-short-cut later to maint).
224+
225+
* "git repack --max-pack-size=8g" stopped being parsed correctly when
226+
the command was reimplemented in C.
227+
(merge b861e23 sb/repack-in-c later to maint).
228+
229+
* An earlier update in v1.8.4.x to "git rev-list --objects" with
230+
negative ref had performance regression.
231+
(merge 200abe7 jk/mark-edges-uninteresting later to maint).
232+
233+
* A recent update to "git send-email" broke platforms where
234+
/etc/ssl/certs/ directory exists, but it cannot used as SSL_ca_path
235+
(e.g. Fedora rawhide).
236+
(merge 01645b7 rk/send-email-ssl-cert later to maint).
237+
238+
* A handful of bugs around interpreting $branch@{upstream} notation
239+
and its lookalike, when $branch part has interesting characters,
240+
e.g. "@", and ":", have been fixed.
241+
(merge 9892d5d jk/interpret-branch-name-fix later to maint).
242+
243+
* "git clone" would fail to clone from a repository that has a ref
244+
directly under "refs/", e.g. "refs/stash", because different
245+
validation paths do different things on such a refname. Loosen the
246+
client side's validation to allow such a ref.
247+
(merge 4c22408 jk/allow-fetch-onelevel-refname later to maint).
248+
249+
* "git log --left-right A...B" lost the "leftness" of commits
250+
reachable from A when A is a tag as a side effect of a recent
251+
bugfix. This is a regression in 1.8.4.x series.
252+
(merge a743528 jc/revision-range-unpeel later to maint).
253+
254+
* documentations to "git pull" hinted there is an "-m" option because
255+
it incorrectly shared the documentation with "git merge".
256+
(merge 08f19cf jc/maint-pull-docfix later to maint).
257+
258+
* "git diff A B submod" and "git diff A B submod/" ought to have done
259+
the same for a submodule "submod", but didn't.
260+
261+
* "git clone $origin foo\bar\baz" on Windows failed to create the
262+
leading directories (i.e. a moral-equivalent of "mkdir -p").
263+
218264
* "submodule.*.update=checkout", when propagated from .gitmodules to
219265
.git/config, turned into a "submodule.*.update=none", which did not
220266
make much sense.

GIT-VERSION-GEN

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
#!/bin/sh
22

33
GVF=GIT-VERSION-FILE
4-
DEF_VER=v1.9-rc0
4+
DEF_VER=v1.9-rc1
55

66
LF='
77
'

0 commit comments

Comments
 (0)