# GIT 1.4.3-rc2 4 messages from 2006-10-10 to 2006-10-10. Participants: Junio C Hamano, Martin Waitz. Thread: https://gitlist.dev/t/5867 ## Junio C Hamano, 2006-10-10 07:11 Subject: GIT 1.4.3-rc2 Message-ID: <7viris63xz.fsf@assigned-by-dhcp.cox.net> URL: https://gitlist.dev/e/7viris63xz.fsf%40assigned-by-dhcp.cox.net ``` I've tagged the tip of master as 1.4.3-rc2. Modulo last minute brown paper bag, I think we are pretty close to the real thing, hopefully should happen this weekend. Changes since 1.4.3-rc1 are as follows; they are mostly fixes as expected (except one thing -- which shows in this list itself). Alan Chandler (2): Update the gitweb/README file to include setting the GITWEB_CONFIG environment Fix usage string to match that given in the man page Alexandre Julliard (2): git.el: Fixed inverted "renamed from/to" message. vc-git.el: Switch to using git-blame instead of git-annotate. Dennis Stosberg (2): lock_ref_sha1_basic does not remove empty directories on BSD Add default values for --window and --depth to the docs Franck Bui-Huu (1): Add git-upload-archive to the main git man page Jakub Narebski (1): gitweb: Cleanup Git logo and Git logo target generation Junio C Hamano (9): Makefile: install and clean merge-recur, still. git-mv: invalidate the removed path properly in cache-tree git-push: .git/remotes/ file does not require SP after colon escape tilde in Documentation/git-rev-parse.txt tar-tree deprecation: we eat our own dog food. gitweb: Make the Git logo link target to point to the homepage git-send-email: avoid uninitialized variable warning. cherry-pick: make -r the default Fix git-revert Luben Tuikov (3): gitweb: Escape ESCAPE (\e) character gitweb: Do not print "log" and "shortlog" redundantly in commit view gitweb: blame: Minimize vertical table row padding Martin Waitz (4): gitweb: document webserver configuration for common gitweb/repo URLs. git-commit: cleanup unused function. git-commit: fix coding style. test-lib: separate individual test better in verbose mode. Nicolas Pitre (1): add commit count options to git-shortlog Petr Baudis (4): Show snapshot link in shortlog only if have_snapsho gitweb: Separate (new) and (deleted) in commitdiff by a space gitweb: Handle commits with empty commit messages more reasonably gitweb: [commit view] Do not suppress commitdiff link in root commit Rene Scharfe (1): git-tar-tree: don't RUN_SETUP Robin Rosenberg (1): Error in test description of t1200-tutorial Yasushi SHOJI (1): gitweb: refactor decode() for utf8 conversion ``` ## Martin Waitz, 2006-10-10 09:39 Subject: Re: GIT 1.4.3-rc2 Message-ID: <20061010093914.GC8612@admingilde.org> URL: https://gitlist.dev/e/20061010093914.GC8612%40admingilde.org In-Reply-To: <7viris63xz.fsf@assigned-by-dhcp.cox.net> ``` hoi :) On Tue, Oct 10, 2006 at 12:11:04AM -0700, Junio C Hamano wrote: > Modulo last minute brown paper bag, I think we are pretty close to the > real thing, hopefully should happen this weekend. very nice! :-) have you looked into the git-fetch --update-head-ok thing I sent last week? -- Martin Waitz ``` ## Junio C Hamano, 2006-10-10 17:42 Subject: Re: GIT 1.4.3-rc2 Message-ID: <7vpsd02hkm.fsf@assigned-by-dhcp.cox.net> URL: https://gitlist.dev/e/7vpsd02hkm.fsf%40assigned-by-dhcp.cox.net In-Reply-To: <20061010093914.GC8612@admingilde.org> ``` Martin Waitz writes: > have you looked into the git-fetch --update-head-ok thing I sent last > week? I remember seeing it and wondering what workflow would need it. Also at the same time I wondered if it was indeed needed for a workflow why that workflow can get away with adding only that option to git-fetch without either adding more things to it or have a custom porcelain that drives the underlying git-fetch-pack directly. In the end I dropped it on the floor because what I wondered about was not clear from the proposed commit log message. ``` ## Martin Waitz, 2006-10-10 17:55 Subject: Re: GIT 1.4.3-rc2 Message-ID: <20061010175501.GD8612@admingilde.org> URL: https://gitlist.dev/e/20061010175501.GD8612%40admingilde.org In-Reply-To: <7vpsd02hkm.fsf@assigned-by-dhcp.cox.net> ``` hoi :) On Tue, Oct 10, 2006 at 10:42:33AM -0700, Junio C Hamano wrote: > > have you looked into the git-fetch --update-head-ok thing I sent last > > week? > > I remember seeing it and wondering what workflow would need it. > Also at the same time I wondered if it was indeed needed for a > workflow why that workflow can get away with adding only that > option to git-fetch without either adding more things to it or > have a custom porcelain that drives the underlying > git-fetch-pack directly. I was wondering about it, too. That's why I haven't added a [PATCH] tag to the message and just added the diff to show the broken part ;-). It is clear that the code as it is now does not work but perhaps the right fix is to simply kill that option. As nobody replied to the message I guess that nobody cares and we can remove it after the release. -- Martin Waitz ```