From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/2] Patches to let Git build with GCC 6 and DEVELOPER=SureWhyNot
Date: Thu, 4 Aug 2016 18:07:00 +0200 (CEST) [thread overview]
Message-ID: <cover.1470326812.git.johannes.schindelin@gmx.de> (raw)
While working on some local setup to allow my poor little laptop to
build and test the Windows-specific patches of Git for Windows on top of
the upstream branches, my development environment updated to use GCC 6,
and these patches were required.
Johannes Schindelin (2):
nedmalloc: fix misleading indentation
nedmalloc: work around overzealous GCC 6 warning
compat/nedmalloc/nedmalloc.c | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
Published-As: https://github.com/dscho/git/releases/tag/gcc-6-v1
Fetch-It-Via: git fetch https://github.com/dscho/git gcc-6-v1
--
2.9.0.281.g286a8d9
base-commit: 80460f513ebd7851953f5402dd9744236128b240
next reply other threads:[~2016-08-04 16:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 16:07 Johannes Schindelin [this message]
2016-08-04 16:07 ` [PATCH 1/2] nedmalloc: fix misleading indentation Johannes Schindelin
2016-08-04 16:07 ` [PATCH 2/2] nedmalloc: work around overzealous GCC 6 warning Johannes Schindelin
2016-08-04 17:41 ` Junio C Hamano
2016-08-05 15:38 ` Johannes Schindelin
2016-08-04 21:56 ` René Scharfe
2016-08-04 22:33 ` Junio C Hamano
2016-08-04 22:39 ` Junio C Hamano
2016-08-05 5:36 ` Johannes Sixt
2016-08-05 5:40 ` Johannes Sixt
2016-08-05 6:24 ` Junio C Hamano
2016-08-05 7:42 ` Jeff King
2016-08-05 15:34 ` Johannes Schindelin
2016-08-05 16:13 ` Junio C Hamano
2016-08-06 8:19 ` Johannes Schindelin
2016-08-05 21:57 ` Junio C Hamano
2016-08-05 22:30 ` René Scharfe
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=cover.1470326812.git.johannes.schindelin@gmx.de \
--to=johannes.schindelin@gmx.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.
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).