From: Max Horn <max@quendi.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org list" <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v2.8.0-rc2
Date: Sat, 12 Mar 2016 10:11:15 +0100 [thread overview]
Message-ID: <006DA180-E4B6-404E-9377-F2BB41F65591@quendi.de> (raw)
In-Reply-To: <xmqqr3fiaq9f.fsf@gitster.mtv.corp.google.com>
> On 11 Mar 2016, at 00:04, Junio C Hamano <gitster@pobox.com> wrote:
>
> A release candidate Git v2.8.0-rc2 is now available for testing
> at the usual places. It is comprised of 459 non-merge commits
> since v2.7.0, contributed by 60 people, 19 of which are new faces.
>
[...]
> Updates since v2.7
> ------------------
>
> UI, Workflows & Features
>
> * It turns out "git clone" over rsync transport has been broken when
> the source repository has packed references for a long time, and
> nobody noticed nor complained about it.
>
> * "branch --delete" has "branch -d" but "push --delete" does not.
This states a problem, but not whether (and how) it was resolved?
[...]
> * Across the transition at around Git version 2.0, the user used to
> get a pretty loud warning when running "git push" without setting
> push.default configuration variable. We no longer warn, given that
> the transition is over long time ago.
That last sentence sounds weird... perhaps "the transition was completed a long time ago" ? Or "the transition ended a long time ago" ?
>
> * README has been renamed to README.md and its contents got tweaked
> slightly to make it easier on the eyes.
>
>
> Performance, Internal Implementation, Development Support etc.
>
> * Add a framework to spawn a group of processes in parallel, and use
> it to run "git fetch --recurse-submodules" in parallel.
>
> * A slight update to the Makefile to mark "phoney" targets
> as such correctly.
phoney -> phony ? (it seems in british english you can write "phoney", but according to a quickly Google search this is rarely used in relation to Makefiles; no surprise, given that the corresponding syntax element is ".PHONY" and you are not allowed to spell it differently ;-)
[...]
>
> * Some calls to strcpy(3) triggers a false warning from static
> analysers that are less intelligent than humans, and reducing the
> number of these false hits helps us notice real issues. A few
> calls to strcpy(3) in test-path-utils that are already safe has
> been rewritten to avoid false wanings.
>
> * Some calls to strcpy(3) triggers a false warning from static
> analysers that are less intelligent than humans, and reducing the
> number of these false hits helps us notice real issues. A few
> calls to strcpy(3) in "git rerere" that are already safe has been
> rewritten to avoid false wanings.
The above two messages are very similar, only the end differs a bit. Perhaps
merge them into one? I.e.. "A few calls to strcpy(3) in test-path-utils and "git rerere" that [...]"
Also: wanings -> warnings
[...]
>
> * Asking gitweb for a nonexistent commit left a warning in the server
> log.
>
> Somebody may want to follow this up with an additional test, perhaps?
> IIRC, we do test that no Perl warnings are given to the server log,
> so this should have been caught if our test coverage were good.
That last paragraph seems odd for a changelog?
[...]
> * The underlying machinery used by "ls-files -o" and other commands
> have been taught not to create empty submodule ref cache for a
have -> has (the machinery is singular)
Cheers,
Max
next prev parent reply other threads:[~2016-03-12 9:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 23:04 [ANNOUNCE] Git v2.8.0-rc2 Junio C Hamano
2016-03-12 9:11 ` Max Horn [this message]
2016-03-14 18:10 ` Junio C Hamano
2016-03-14 15:29 ` Michael J Gruber
2016-03-14 15:30 ` [PATCH] wt-status: allow "ahead " to be picked up by l10n Michael J Gruber
2016-03-14 15:57 ` Junio C Hamano
2016-03-14 15:56 ` [ANNOUNCE] Git v2.8.0-rc2 Junio C Hamano
2016-03-14 17:47 ` Junio C Hamano
2016-03-16 13:33 ` Michael J Gruber
2016-03-16 13:40 ` Duy Nguyen
2016-03-16 15:32 ` Michael J Gruber
2016-03-16 16:30 ` Junio C Hamano
2016-03-17 14:51 ` Michael J Gruber
2016-03-17 15:14 ` [RFC/PATCH] Makefile: allow po generation through po target Michael J Gruber
2016-03-17 22:42 ` Junio C Hamano
2016-03-17 16:15 ` [ANNOUNCE] Git v2.8.0-rc2 Junio C Hamano
2016-03-20 9:45 ` Jiang Xin
2016-03-20 15:11 ` Michael J Gruber
2016-03-21 20:01 ` Junio C Hamano
2016-03-22 10:00 ` Michael J Gruber
2016-03-22 17:43 ` Junio C Hamano
2016-03-15 16:42 ` 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
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=006DA180-E4B6-404E-9377-F2BB41F65591@quendi.de \
--to=max@quendi.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).