From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] Git 1.7.6.rc1
Date: Wed, 08 Jun 2011 20:14:41 -0700 [thread overview]
Message-ID: <7vlixbzof2.fsf@alter.siamese.dyndns.org> (raw)
A release candidate Git 1.7.6-rc1 is available at the usual places
for testing:
http://www.kernel.org/pub/software/scm/git/
git-1.7.6.rc1.tar.{gz,bz2} (source tarball)
git-htmldocs-1.7.6.rc1.tar.{gz,bz2} (preformatted docs)
git-manpages-1.7.6.rc1.tar.{gz,bz2} (preformatted docs)
The RPM binary packages for a few architectures are found in:
testing/git-*-1.7.6.rc1-1.fc13.$arch.rpm (RPM)
A week has passed since the casual "-rc0" was tagged, so here is the first
official release candidate, with RPM and announcement.
Please switch to the tip of 'master' for your daily use so that we can
ship 1.7.6 without regressions and bugs in new features in two weeks.
Thanks.
----------------------------------------------------------------
Changes since v1.7.6-rc0 are as follows:
Alex Riesen (1):
t3703: skip more tests using colons in file names on Windows
Brandon Casey (2):
t7508: demonstrate status's failure to use --porcelain format with -z
builtin/commit.c: set status_format _after_ option parsing
Jakub Narebski (4):
gitweb: Move information about installation from README to INSTALL
gitweb: Describe CSSMIN and JSMIN in gitweb/INSTALL
gitweb: Move "Requirements" up in gitweb/INSTALL
gitweb: Fix usability of $prevent_xss
Jeff King (1):
diff_tree: disable QUICK optimization with diff filter
Jim Meyering (1):
fetch: do not leak a refspec
Junio C Hamano (2):
diff: futureproof "stop feeding the backend early" logic
Git 1.7.6-rc1
reply other threads:[~2011-06-09 3:14 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=7vlixbzof2.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®