From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] GIT 1.2.1
Date: Wed, 15 Feb 2006 22:25:59 -0800 [thread overview]
Message-ID: <7vzmkrizuw.fsf@assigned-by-dhcp.cox.net> (raw)
The latest maintenance release GIT 1.2.1 is available at the
usual places:
http://www.kernel.org/pub/software/scm/git/
git-1.2.1.tar.{gz,bz2} (tarball)
RPMS/$arch/git-*-1.2.1-1.$arch.rpm (RPM)
Nothing earth-shattering but cleanups and cleanups and cleanups.
All the interesting things are happening in "master" and "pu",
which will be a topic for a separate message.
----------------------------------------------------------------
Changes since v1.2.0 are as follows:
Fernando J. Pereda:
Print an error if cloning a http repo and NO_CURL is set
Fredrik Kuivinen:
s/SHELL/SHELL_PATH/ in Makefile
Josef Weidendorfer:
More useful/hinting error messages in git-checkout
Junio C Hamano:
Documentation: git-commit in 1.2.X series defaults to --include.
Documentation: git-ls-files asciidocco.
bisect: remove BISECT_NAMES after done.
combine-diff: diff-files fix.
combine-diff: diff-files fix (#2)
checkout: fix dirty-file display.
next reply other threads:[~2006-02-16 6:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 6:25 Junio C Hamano [this message]
2006-02-16 6:47 Brown, Len
2006-02-16 21:41 ` Greg KH
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=7vzmkrizuw.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
Powered by JetHome