From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: I've tagged 1.4.3-rc3 but there is a last-minute monkey wrench...
Date: Sun, 15 Oct 2006 01:04:28 -0700 [thread overview]
Message-ID: <7vvemmypgz.fsf@assigned-by-dhcp.cox.net> (raw)
Changes since -rc2 are mostly fixes:
- Christian Couder fixed the tracing facility so that
"GIT_TRACE= git-foo" and "unset GIT_TRACE; git-foo" to
behave the same;
- Assorted git-svn fixes from Eric Wong;
- Johannes fixed "diff -w -b";
- Also Johannes has two fixes to cvsserver;
- http-fetch transport does not use webdav to discover remote
refs anymore;
- breakage in generating RPM (perl-Git) has been fixed;
- "git-apply --numstat -z" did not terminate line with NUL -- fixed;
- Martin Waitz made "git diff" to run pager by default;
- Nicolas Pitre made sideband remote messages to be written out
with single write(2) to prevent them from being broken up;
- Rene Scharfe has a good API clean-up: hash_sha1_file();
- Yasushi SHOJI noticed and fixed that "git-clone" did not
correctly handle the origin repository specified as a
relative directory; it treated it relative to the new
repository not the directory the command was started from.
But there is already one commit that is rather important on the
"master" branch after -rc3. It is needed so that we do not
break git older than v1.2.0 (Feb 12, 2006).
I am still hoping we can declare v1.4.3 on coming Wednesday,
unless it is eaten by my day job (which is unfortunately not so
unusual for me these days), in which case we would have to defer
it until next weekend.
reply other threads:[~2006-10-15 8:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vvemmypgz.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox