From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] GIT 1.4.4.2
Date: Sat, 09 Dec 2006 13:13:34 -0800 [thread overview]
Message-ID: <7vu004ai2p.fsf@assigned-by-dhcp.cox.net> (raw)
The latest maintenance release GIT 1.4.4.2 has been available at
the usual places for a few days, but vger seems to have eaten
the message I sent out, so here is a resend:
http://www.kernel.org/pub/software/scm/git/
git-1.4.4.2.tar.{gz,bz2} (tarball)
git-htmldocs-1.4.4.2.tar.{gz,bz2} (preformatted docs)
git-manpages-1.4.4.2.tar.{gz,bz2} (preformatted docs)
RPMS/$arch/git-*-1.4.4.2-1.$arch.rpm (RPM)
This contains a handful fixes since 1.4.4.1; nothing earth
shattering.
----------------------------------------------------------------
Changes since v1.4.4.1 are as follows:
Alex Riesen (1):
git-blame: fix rev parameter handling.
Andy Parkins (2):
Increase length of function name buffer
Document git-repo-config --bool/--int options.
Eric Wong (4):
git-svn: error out from dcommit on a parent-less commit
git-svn: correctly handle revision 0 in SVN repositories
git-svn: preserve uncommitted changes after dcommit
git-svn: avoid fetching files twice in the same revision
Johannes Schindelin (1):
git-mv: search more precisely for source directory in index
Junio C Hamano (5):
git blame -C: fix output format tweaks when crossing file boundary.
tutorial: talk about user.name early and don't start with commit -a
receive-pack: do not insist on fast-forward outside refs/heads/
unpack-trees: make sure "df_conflict_entry.name" is NUL terminated.
git-reset to remove "$GIT_DIR/MERGE_MSG"
René Scharfe (1):
archive-zip: don't use sizeof(struct ...)
reply other threads:[~2006-12-09 21:13 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=7vu004ai2p.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