1GIT v1.5.1 Release Notes 2======================== 3 4Updates since v1.5.0 5-------------------- 6 7* Deprecated commands and options. 8 9 - git-diff-stages and git-resolve have been removed. 10 11* New commands and options. 12 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 17 chronological order. 18 19 - "git diff" learned --ignore-space-at-eol. This is a weaker 20 form of --ignore-space-change. 21 22 - "git diff --no-index pathA pathB" can be used as diff 23 replacement with git specific enhancements. 24 25 - "git name-rev" learned --refs=<pattern>, to limit the tags 26 used for naming the given revisions only to the ones 27 matching the given pattern. 28 29 - "git remote update" is to run "git fetch" for defined remotes 30 to update tracking branches. 31 32 - "git cvsimport" can now take '-d' to talk with a CVS 33 repository different from what are recorded in CVS/Root 34 (overriding it with environment CVSROOT does not work). 35 36 - "git bundle" can help sneaker-netting your changes between 37 repositories. 38 39 40* Updated behaviour of existing commands. 41 42 - git-svn got almost a rewrite. 43 44 - core.autocrlf configuration, when set to 'true', makes git 45 to convert CRLF at the end of lines in text files to LF when 46 reading from the filesystem, and convert in reverse when 47 writing to the filesystem. The variable can be set to 48 'input', in which case the conversion happens only while 49 reading from the filesystem but files are written out with 50 LF at the end of lines. Currently, which paths to consider 51 'text' (i.e. be subjected to the autocrlf mechanism) is 52 decided purely based on the contents, but the plan is to 53 allow users to explicitly override this heuristic based on 54 paths. 55 56 - The behaviour of 'git-apply', when run in a subdirectory, 57 without --index nor --cached were inconsistent with that of 58 the command with these options. This was fixed to match the 59 behaviour with --index. A patch that is meant to be applied 60 with -p1 from the toplevel of the project tree can be 61 applied with any custom -p<n> option. A patch that is not 62 relative to the toplevel needs to be applied with -p<n> 63 option with or without --index (or --cached). 64 65 - "git diff" outputs a trailing HT when pathnames have embedded 66 SP on +++/--- header lines, in order to help "GNU patch" to 67 parse its output. "git apply" was already updated to accept 68 this modified output format since ce74618d (Sep 22, 2006). 69 70 - "git cvsserver" runs hooks/update and honors its exit status. 71 72 - "git cvsserver" can be told to send everything with -kb. 73 74 - "git diff --check" also honors the --color output option. 75 76 - "git name-rev" used to stress the fact that a ref is a tag too 77 much, by saying something like "v1.2.3^0~22". It now says 78 "v1.2.3~22" in such a case (it still says "v1.2.3^0" if it does 79 not talk about an ancestor of the commit that is tagged, which 80 makes sense). 81 82 - "git rev-list --boundary" now shows boundary markers for the 83 commits omitted by --max-age and --max-count condition. 84 85 - The configuration mechanism now reads $(prefix)/etc/gitconfig. 86 87 - "git apply --verbose" shows what preimage lines were wanted 88 when it couldn't find them. 89 90 - "git status" in a read-only repository got a bit saner. 91 92* Hooks 93 94 - The sample update hook to show how to send out notification 95 e-mail was updated to show only new commits that appeared in 96 the repository. Earlier, it showed new commits that appeared 97 on the branch. 98 99-- 100exec >/var/tmp/1 101O=v1.5.0.2-259-g16d5315 102echo O=`git describe master` 103git shortlog --no-merges $O..master ^maint 104 105# Local Variables: 106# mode: text 107# End: