From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] Git v1.7.10.5
Date: Sun, 17 Jun 2012 15:24:18 -0700 [thread overview]
Message-ID: <7vd34x60h9.fsf@alter.siamese.dyndns.org> (raw)
The latest maintenance release Git v1.7.10.5 is now available at
the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
9d0767ef195d3971a891efaf11996158cb341499 git-1.7.10.5.tar.gz
3f205417f11a9ae478eb77541df483a8fc4a4bc8 git-htmldocs-1.7.10.5.tar.gz
2249a6481891a349ed9a11dec89a35afec9f9edb git-manpages-1.7.10.5.tar.gz
Also the following public repositories all have a copy of the v1.7.10.5
tag and the maint branch that the tag points at:
url = git://repo.or.cz/alt-git.git
url = https://code.google.com/p/git-core/
url = git://git.sourceforge.jp/gitroot/git-core/git.git
url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core
url = https://github.com/gitster/git
This time I didn't forget to update DEF_VER in GIT-VERSION-FILE ;-)
Git v1.7.10.5 Release Notes
===========================
Fixes since v1.7.10.4
---------------------
* "git fast-export" did not give a readable error message when the
same mark erroneously appeared twice in the --import-marks input.
* "git rebase -p" used to pay attention to rebase.autosquash which
was wrong. "git rebase -p -i" should, but "git rebase -p" by
itself should not.
----------------------------------------------------------------
Changes since v1.7.10.4 are as follows:
Johannes Schindelin (1):
fast-export: report SHA-1 instead of gibberish when marks exist already
Junio C Hamano (1):
Git 1.7.10.5
Vincent van Ravesteijn (1):
Do not autosquash in case of an implied interactive rebase
reply other threads:[~2012-06-17 22:24 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=7vd34x60h9.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--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
all inboxes | Powered by JetHome®