-
v1.4.3.2a153adf6 · ·
GIT 1.4.3.2 This is primarily to fix two major issues discovered post 1.4.3.1 release. - The pager change to default to LESS=FRS exposed problem with less that switches to alternate screen, shows its output and then switches back immediately from the alternate screen afterwards -- which means the user would not have a chance to see _anything_. - Older upload-pack protocol clients did not pass host= and recent git-daemon change to support virtual hosting did not handle this correctly (although it attempted to do so, the check was borked). Alexandre Julliard (1): prune-packed: Fix uninitialized variable. J. Bruce Fields (1): Make prune also run prune-packed Jakub Narebski (2): gitweb: Whitespace cleanup - tabs are for indent, spaces are for align (2) gitweb: Do not esc_html $basedir argument to git_print_tree_entry Jim Meyering (2): git-clone: honor --quiet xdiff/xemit.c (xdl_find_func): Elide trailing white space in a context header. Junio C Hamano (2): pager: default to LESS=FRSX not LESS=FRS daemon: do not die on older clients. Karl Hasselström (1): git-vc: better installation instructions Lars Hjemli (1): Fix usagestring for git-branch Petr Baudis (1): gitweb: Fix setting $/ in parse_commit() Rene Scharfe (1): git-merge: show usage if run without arguments Santi Béjar (1): Documentation for the [remote] config
-
v1.4.2-rc4943d5b73 · ·
GIT 1.4.2-rc4 It's been a week since -rc3, so here it is. The changes are really small fixes and nothing else. Let's hope I can tag the real 1.4.2 this weekend.
-
v1.4.1-rc2abc02670 · ·
GIT 1.4.1-rc2 Many fixes since v1.4.1-rc1 was issued. Notable are: - git-cvsimport to manage multiple branches are (hopefully) fixed now (Martin and Johannes). - git-rebase learned how to use 3-way merge backends by "git-rebase --merge" (Eric Wong). - git-svn updates (Eric Wong). - "git-commit -m" breakage was fixed (me).
-
v1.4.1-rc1bf9e9542 · ·
GIT 1.4.1-rc1 As promised, 1.4.X series will be managed slightly differently, and this is in preparation of the first installment of it. The releases will come from the "master" branch to contain both fixes and enhancements from now on. Hotfix releases when necessary would have 1.4.X.Y revision numbers, but I am hoping that we do not have to do that very often. Since all the exciting and potentially risky developments are to happen on the "next" branch and they are supposed to graduate to "master" branch after they are reasonably well cooked, this change will help the end-users to stay reasonably current without hopefully not introducing unexpected problems. The older scheme left out all the enhancements if people followed packaged versions, and gave big surprises when upgrading from version X.Y.Z to X.(Y+1).0 which was not so nice.