From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Delaying 2.0 final
Date: Fri, 16 May 2014 15:45:10 -0700 [thread overview]
Message-ID: <xmqqd2fd8hs9.fsf@gitster.dls.corp.google.com> (raw)
As we seem to have a few regressions we may want to fix, I will not
be cutting the 2.0 final today (https://tinyurl.com/gitCal).
I queued the following near the bottom of 'pu' (these are also
merged to 'next' to keep pu^{/match.next} in sync with next), and
plan to cut 2.0.0-rc4 early next week.
* git-gui has a show-stopper bug that wants to see if it is used
with a version of git that "vsatisfies" 1.7.0; because 2.x is
considered significantly different, it incorrectly decides to use
the codepath for ancient versions that compares older than 1.7.0
when working inside a submodule working tree. A fix by Jens
Lehmann is queued as an emergency patch to use vcompare instead.
* There was a vague admission of having broken git-remote-hg/bzr by
its author that hinted one topic branch is the culprit, without
much detail. As a precautionary measure, the merge of the topic
has been reverted.
* git-remote-hg/bzr are maintained outside our tree, our copy will
become stale and will eventually go away. A warning message to
its standard error output has been added to each of them to tell
the users where to find the latest of these tools.
* git-request-pull has a minor regression and lost a useful DWIM
that was designed to be friendly to users of Git older than
1.7.10. "git request-pull $base $URL for-linus" used to say
"Please pull tags/for-linus" if that is what the user meant, but
the version in 2.0.0-rc3 requires the command line to be "git
request-pull $base $URL tags/for-linus". It is simple enough to
special case this use case, and a patch is included to fix it
with a band-aid.
If you fetch tonight's 'pu' branch, you will find all of the above
at f608b83. Hopefully 2.0.0-rc4 and 2.0.0-final will be the same
tree as that commit, with updated release notes.
next reply other threads:[~2014-05-16 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 22:45 Junio C Hamano [this message]
2014-05-18 0:31 ` Delaying 2.0 final Jiang Xin
2014-05-18 0:36 ` Jiang Xin
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=xmqqd2fd8hs9.fsf@gitster.dls.corp.google.com \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.