git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [ANNOUNCE] Git 1.6.6.rc4
Date: Sun, 20 Dec 2009 14:59:47 -0800	[thread overview]
Message-ID: <7vmy1d9rq4.fsf@alter.siamese.dyndns.org> (raw)

A release candidate Git 1.6.6.rc4 is available at the usual places
for final testing:

  http://www.kernel.org/pub/software/scm/git/

  git-1.6.6.rc4.tar.{gz,bz2}			(source tarball)
  git-htmldocs-1.6.6.rc4.tar.{gz,bz2}		(preformatted docs)
  git-manpages-1.6.6.rc4.tar.{gz,bz2}		(preformatted docs)

The RPM binary packages for a few architectures are found in:

  testing/git-*-1.6.6.rc4-1.fc11.$arch.rpm	(RPM)

Hopefully I'll do the final this Wednesday to make 1.6.6 a holiday gift to
everybody.

I would very much prefer news outlets like kernelpodcast.org and lwn.net
_not_ to say "... is released; it comes with many _fixes_".  Fixes to
released versions have indeed been included in the 'master' branch, but
they all appear in the maintenance release.  The main _point_ of using a
new feature release like 1.6.6 is to get new _features_, so it is more
appropriate to say "it comes with many new features."

Thanks for all contributors who have worked hard to whip this release into
shape.

----------------------------------------------------------------

Changes since v1.6.6-rc3 are as follows:

Björn Gustavsson (1):
      rebase -i: abort cleanly if the editor fails to launch

Eric Wong (2):
      git svn: make empty directory creation gc-aware
      t9146: use 'svn_cmd' wrapper

Junio C Hamano (1):
      Git 1.6.6-rc4

Stephen Boyd (2):
      api-strbuf.txt: fix typos and document launch_editor()
      technical-docs: document hash API

                 reply	other threads:[~2009-12-20 23:00 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vmy1d9rq4.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).