From: Junio C Hamano <gitster@pobox.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v1.8.4
Date: Mon, 26 Aug 2013 20:42:19 -0700 [thread overview]
Message-ID: <xmqq38pviyuc.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <alpine.LFD.2.03.1308232242180.14472@syhkavp.arg> (Nicolas Pitre's message of "Mon, 26 Aug 2013 20:06:37 -0400 (EDT)")
Nicolas Pitre <nico@fluxnic.net> writes:
> On Fri, 23 Aug 2013, Junio C Hamano wrote:
>
>> The latest feature release Git v1.8.4 is now available at the usual
>> places. It contains 870+ changes from ~100 contributors (among
>> which 33 people are new) since v1.8.3.
>>
>> We will have two more releases til the end of this year; the release
>> after that could be Git 2.0.
>
> May I land a big teaser for a possible Git 2.0 feature?
;-)
It is not even any remotely controversial feature that has to wait
until 2.0 boundary to potentially break established usage aka
inertia.
Happy.
prev parent reply other threads:[~2013-08-27 3:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 21:51 [ANNOUNCE] Git v1.8.4 Junio C Hamano
2013-08-27 0:06 ` Nicolas Pitre
2013-08-27 0:40 ` Duy Nguyen
2013-08-27 4:05 ` Nicolas Pitre
2013-08-27 3:42 ` 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=xmqq38pviyuc.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
/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;
as well as URLs for NNTP newsgroup(s).