From: "Martin Ågren" <martin.agren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH v2 1/3] RelNotes 2.20: move some items between sections
Date: Tue, 4 Dec 2018 06:43:17 +0100 [thread overview]
Message-ID: <961bfc2ad69e6a27ad68c6a4f0e92232f13c33f8.1543901498.git.martin.agren@gmail.com> (raw)
In-Reply-To: <cover.1543901498.git.martin.agren@gmail.com>
Some items that should be in "Performance, Internal Implementation,
Development Support etc." have ended up in "UI, Workflows & Features".
Move them, and do s/uses/use/ while at it.
Signed-off-by: Martin Ågren <martin.agren@gmail.com>
---
Documentation/RelNotes/2.20.0.txt | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/RelNotes/2.20.0.txt b/Documentation/RelNotes/2.20.0.txt
index b1deaf37da..f4e79c4cfb 100644
--- a/Documentation/RelNotes/2.20.0.txt
+++ b/Documentation/RelNotes/2.20.0.txt
@@ -137,11 +137,6 @@ UI, Workflows & Features
command line, or setting sendemail.suppresscc configuration
variable to "misc-by", can be used to disable this behaviour.
- * Developer builds now uses -Wunused-function compilation option.
-
- * One of our CI tests to run with "unusual/experimental/random"
- settings now also uses commit-graph and midx.
-
* "git mergetool" learned to take the "--[no-]gui" option, just like
"git difftool" does.
@@ -185,6 +180,11 @@ UI, Workflows & Features
Performance, Internal Implementation, Development Support etc.
+ * Developer builds now use -Wunused-function compilation option.
+
+ * One of our CI tests to run with "unusual/experimental/random"
+ settings now also uses commit-graph and midx.
+
* When there are too many packfiles in a repository (which is not
recommended), looking up an object in these would require
consulting many pack .idx files; a new mechanism to have a single
--
2.20.0.rc2.1.gc81af441bb
next prev parent reply other threads:[~2018-12-04 5:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 14:58 [ANNOUNCE] Git v2.20.0-rc2 Junio C Hamano
2018-12-03 20:21 ` [PATCH 0/3] " Martin Ågren
2018-12-03 20:21 ` [PATCH 1/3] RelNotes 2.20: move some items between sections Martin Ågren
2018-12-04 2:23 ` Junio C Hamano
2018-12-04 5:43 ` Martin Ågren
2018-12-04 5:43 ` Martin Ågren [this message]
2018-12-04 5:43 ` [PATCH v2 2/3] RelNotes 2.20: clarify sentence Martin Ågren
2018-12-04 5:43 ` [PATCH v2 3/3] RelNotes 2.20: drop spurious double quote Martin Ågren
2018-12-03 20:21 ` [PATCH 2/3] RelNotes 2.20: clarify sentence Martin Ågren
2018-12-04 2:23 ` Junio C Hamano
2018-12-03 20:21 ` [PATCH 3/3] RelNotes 2.20: drop spurious double quote Martin Ågren
2018-12-04 2:26 ` Junio C Hamano
2018-12-03 20:45 ` [ANNOUNCE] Git v2.20.0-rc2 Johannes Schindelin
2018-12-04 19:39 ` Ævar Arnfjörð Bjarmason
2018-12-05 2:48 ` Stefan Beller
2018-12-05 4:05 ` Jeff King
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=961bfc2ad69e6a27ad68c6a4f0e92232f13c33f8.1543901498.git.martin.agren@gmail.com \
--to=martin.agren@gmail.com \
--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).