git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v2.14.0-rc0
Date: Mon, 17 Jul 2017 13:41:57 -0700	[thread overview]
Message-ID: <xmqq7ez6hk2y.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <87mv8638y5.fsf@gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Sat, 15 Jul 2017 01:17:06 +0200")

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

> On Thu, Jul 13 2017, Junio C. Hamano jotted:
>
> Proposed improvements for the release notes (is this a good way to
> propose RelNotes changes?)

Thanks.  You could also throw a patch just like any bugfix/update
to documentation, I would think.

> I think this may explain it better:
>
>  * The "[includeIf "gitdir:$dir"] path=..." mechanism introduced in
>    2.13.0 would canonicalize the path of the gitdir being
>    matched.
>
>    Therefore it wouldn't match e.g. "gitdir:~/work/*" against a repo in
>    "~/work/main" if ~/work was a symlink to "/mnt/storage/work".
>
>    Now we match both the resolved canonical path and what "pwd" would
>    show. The include will happen if either one matches.

Will use this (and some others) verbatim ;-)  Thanks.

>>  * Update "perl-compatible regular expression" support to enable JIT
>>    and also allow linking with the newer PCRE v2 library.
>
> At the risk of advertising work I've done too much, I think it makes
> sense to split this into two separate and somewhat more verbose items:

As I shoot for shorter summary, going down to too much detail in
these entries is not welcome.

However, an exception is the top part of the release notes where we
discuss backward incompatible changes etc. that helps people to
decide the deployment strategy.  Encouraging migration from v1 to v2
belongs there, I would think.

  parent reply	other threads:[~2017-07-17 20:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13 23:43 [ANNOUNCE] Git v2.14.0-rc0 Junio C Hamano
2017-07-14 23:17 ` Ævar Arnfjörð Bjarmason
2017-07-15  4:09   ` Christian Couder
2017-07-15 10:09     ` Ævar Arnfjörð Bjarmason
2017-07-17 20:41   ` Junio C Hamano [this message]
2017-07-18 20:03     ` Junio C Hamano
2017-07-20 14:19     ` [PATCH 0/6] 2.14 RelNotes improvements Ævar Arnfjörð Bjarmason
2017-07-20 20:35       ` Junio C Hamano
2017-07-21 11:03         ` Ævar Arnfjörð Bjarmason
2017-07-20 14:19     ` [PATCH 1/6] RelNotes: mention "log: add -P as a synonym for --perl-regexp" Ævar Arnfjörð Bjarmason
2017-07-20 14:19     ` [PATCH 2/6] RelNotes: mention "log: make --regexp-ignore-case work with --perl-regexp" Ævar Arnfjörð Bjarmason
2017-07-20 14:19     ` [PATCH 3/6] RelNotes: mention "sha1dc: optionally use sha1collisiondetection as a submodule" Ævar Arnfjörð Bjarmason
2017-07-20 14:19     ` [PATCH 4/6] RelNotes: mention that PCRE v2 exposes the same syntax Ævar Arnfjörð Bjarmason
2017-07-20 15:24       ` Junio C Hamano
2017-07-20 14:19     ` [PATCH 5/6] RelNotes: remove duplicate mention of PCRE v2 Ævar Arnfjörð Bjarmason
2017-07-20 15:26       ` Junio C Hamano
2017-07-20 14:19     ` [PATCH 6/6] RelNotes: add more notes about PCRE in 2.14 Ævar Arnfjörð Bjarmason
2017-07-20 19:11       ` Junio C Hamano

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=xmqq7ez6hk2y.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@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).