1 GIT v1.5.1 Release Notes
2 ========================
7 * Deprecated commands and options.
9 - git-diff-stages and git-resolve have been removed.
11 * New commands and options.
13 - "git log" and friends take --reverse. This makes output
14 that typically goes reverse order in chronological order.
15 "git shortlog" usually lists commits in chronological order,
16 but with "--reverse", they are shown in reverse
19 - "git diff" learned --ignore-space-at-eol. This is a weaker
20 form of --ignore-space-change.
22 - "git diff --no-index pathA pathB" can be used as diff
23 replacement with git specific enhancements.
25 - "git diff --pretty=format:<string>" to allow more flexible
28 - "git name-rev" learned --refs=<pattern>, to limit the tags
29 used for naming the given revisions only to the ones
30 matching the given pattern.
32 - "git remote update" is to run "git fetch" for defined remotes
33 to update tracking branches.
35 - "git cvsimport" can now take '-d' to talk with a CVS
36 repository different from what are recorded in CVS/Root
37 (overriding it with environment CVSROOT does not work).
39 - "git bundle" can help sneaker-netting your changes between
42 - A new configuration "core.symlinks" can be used to disable
43 symlinks on filesystems that do not support them; they are
44 checked out as regular files instead.
47 * Updated behaviour of existing commands.
49 - git-svn got almost a rewrite.
51 - core.autocrlf configuration, when set to 'true', makes git
52 to convert CRLF at the end of lines in text files to LF when
53 reading from the filesystem, and convert in reverse when
54 writing to the filesystem. The variable can be set to
55 'input', in which case the conversion happens only while
56 reading from the filesystem but files are written out with
57 LF at the end of lines. Currently, which paths to consider
58 'text' (i.e. be subjected to the autocrlf mechanism) is
59 decided purely based on the contents, but the plan is to
60 allow users to explicitly override this heuristic based on
63 - The behaviour of 'git-apply', when run in a subdirectory,
64 without --index nor --cached were inconsistent with that of
65 the command with these options. This was fixed to match the
66 behaviour with --index. A patch that is meant to be applied
67 with -p1 from the toplevel of the project tree can be
68 applied with any custom -p<n> option. A patch that is not
69 relative to the toplevel needs to be applied with -p<n>
70 option with or without --index (or --cached).
72 - "git diff" outputs a trailing HT when pathnames have embedded
73 SP on +++/--- header lines, in order to help "GNU patch" to
74 parse its output. "git apply" was already updated to accept
75 this modified output format since ce74618d (Sep 22, 2006).
77 - "git cvsserver" runs hooks/update and honors its exit status.
79 - "git cvsserver" can be told to send everything with -kb.
81 - "git diff --check" also honors the --color output option.
83 - "git name-rev" used to stress the fact that a ref is a tag too
84 much, by saying something like "v1.2.3^0~22". It now says
85 "v1.2.3~22" in such a case (it still says "v1.2.3^0" if it does
86 not talk about an ancestor of the commit that is tagged, which
89 - "git rev-list --boundary" now shows boundary markers for the
90 commits omitted by --max-age and --max-count condition.
92 - The configuration mechanism now reads $(prefix)/etc/gitconfig.
94 - "git apply --verbose" shows what preimage lines were wanted
95 when it couldn't find them.
97 - "git status" in a read-only repository got a bit saner.
99 - "git fetch" (hence "git clone" and "git pull") are less
100 noisy when the output does not go to tty.
104 - The sample update hook to show how to send out notification
105 e-mail was updated to show only new commits that appeared in
106 the repository. Earlier, it showed new commits that appeared
111 O=v1.5.0.3-268-g3ddad98
112 echo O=`git describe master`
113 git shortlog --no-merges $O..master ^maint
projects / thirdparty / git.git / blob