Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: git@vger.kernel.org
Subject: Re: Git 1.1.6?
Date: Sat, 04 Feb 2006 20:50:40 -0800	[thread overview]
Message-ID: <7vd5i2s927.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <43E55B69.1070601@zytor.com> (H. Peter Anvin's message of "Sat, 04 Feb 2006 17:56:57 -0800")

"H. Peter Anvin" <hpa@zytor.com> writes:

> I see git-1.1.6 is out, but I haven't seen an announcement?  What's up?

Not much.

I was planning to do a 1.2.0 soon enough for 1.1.6 to matter in
practice, but that has plan been slipping for various reasons.

Changes between 1.1.5 and 1.1.6 are primarily docs and do not
affect functionality.

---

Fredrik Kuivinen:
      merge-recursive: Improve the error message printed when merge(1) isn't found.
      git-branch: Documentation fixes

J. Bruce Fields:
      git push -f documentation

Junio C Hamano:
      pre-commit sample hook: do not barf on the initial import
      GIT 1.1.6

      reply	other threads:[~2006-02-05  4:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-05  1:56 Git 1.1.6? H. Peter Anvin
2006-02-05  4:50 ` Junio C Hamano [this message]

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=7vd5i2s927.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=hpa@zytor.com \
    /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