From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "René Scharfe" <l.s.r@web.de>, git@vger.kernel.org
Subject: Re: [PATCH 2/2] nedmalloc: work around overzealous GCC 6 warning
Date: Sat, 6 Aug 2016 10:19:52 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1608061014170.5786@virtualbox> (raw)
In-Reply-To: <xmqqpopnxkfv.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Fri, 5 Aug 2016, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > This setup will from now on test next & pu in the Git for Windows SDK, and
> > rebase Git for Windows' current master to git.git's maint, master, next &
> > pu, every morning after a weekday (unless I forget to turn on my laptop,
> > that is).
>
> Sounds really good. Thanks.
Report for today:
- `pu` and `next` pass
- rebasing the Windows-specific patches failed because of the merge
conflicts when trying to apply the GCC-6 pragma, which I have on Git for
Windows' `master` already.
Note: I fixed said merge conflicts locally, and the way I set this up, the
CI job learns the conflict resolution and will apply it automatically next
time it runs.
So: all greeeeen today.
Ciao,
Dscho
next prev parent reply other threads:[~2016-08-06 21:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 16:07 [PATCH 0/2] Patches to let Git build with GCC 6 and DEVELOPER=SureWhyNot Johannes Schindelin
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 [this message]
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=alpine.DEB.2.20.1608061014170.5786@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=l.s.r@web.de \
/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).