On Fri, Oct 2, 2015 at 1:05 PM, Marek Polacek <pola...@redhat.com> wrote:
>
> I'd like to backport the following patch to the gcc-5 branch. The
> problem here is that there's a bug in the gcc-5 branch due to which
> we aren't able to warn for
> int foo (void) { return NULL; }
> in C. I have a patch for this issue, but I can't backport it without
> the following patch, because otherwise the libgo build would fail.
>
> Should I just commit the patch without the MERGE hunk?
Yes--go ahead.
> Or would you rather do it by yourself?
No, there is no need for that. I do the commits to trunk because the
master sources live on go-review.googlesource.com. But I don't try to
track the GCC branches in that repo, so you can just commit the change
directly.
Thanks.
Ian
