From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] GIT 1.4.3.5
Date: Sat, 11 Nov 2006 21:23:20 -0800 [thread overview]
Message-ID: <7v64dli6gn.fsf@assigned-by-dhcp.cox.net> (raw)
The latest maintenance release GIT 1.4.3.5 is available at the
usual places:
http://www.kernel.org/pub/software/scm/git/
git-1.4.3.5.tar.{gz,bz2} (tarball)
git-htmldocs-1.4.3.5.tar.{gz,bz2} (preformatted docs)
git-manpages-1.4.3.5.tar.{gz,bz2} (preformatted docs)
RPMS/$arch/git-*-1.4.3.5-1.$arch.rpm (RPM)
The 'master' front has been very quiet and it will hopefully
soon produce 1.4.4 but in the meantime here is primarily to fix
git-svn correctness issues.
----------------------------------------------------------------
Changes since v1.4.3.4 are as follows:
Alex Riesen (1):
merge-recursive implicitely depends on trust_executable_bit
Eric Wong (3):
git-svn: avoid printing filenames of files we're not tracking
git-svn: don't die on rebuild when --upgrade is specified
git-svn: fix dcommit losing changes when out-of-date from svn
Jakub Narebski (1):
Documentation: Transplanting branch with git-rebase --onto
Jeff King (1):
Fix git-runstatus for repositories containing a file named HEAD
Junio C Hamano (3):
adjust_shared_perm: chmod() only when needed.
path-list: fix path-list-insert return value
git-cvsserver: read from git with -z to get non-ASCII pathnames.
Petr Baudis (1):
Nicer error messages in case saving an object to db goes wrong
Robert Shearman (1):
git-rebase: Use --ignore-if-in-upstream option when executing git-format-patch.
Tero Roponen (1):
remove an unneeded test
reply other threads:[~2006-11-12 5:23 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=7v64dli6gn.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=linux-kernel@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