On Wed, 22 Aug 2018, Uecker, Martin wrote:
> Am Dienstag, den 21.08.2018, 21:34 + schrieb Joseph Myers:
> > On Tue, 21 Aug 2018, Uecker, Martin wrote:
> >
> > > > I don't see why this is target-specific (if it is, the documentation
> > > > for
> > > > users in invoke.texi should explain wha
Am Dienstag, den 21.08.2018, 21:34 + schrieb Joseph Myers:
> On Tue, 21 Aug 2018, Uecker, Martin wrote:
>
> > > I don't see why this is target-specific (if it is, the documentation for
> > > users in invoke.texi should explain what targets it works for and what it
> > > doesn't work for) any
On Tue, 21 Aug 2018, Uecker, Martin wrote:
> > I don't see why this is target-specific (if it is, the documentation for
> > users in invoke.texi should explain what targets it works for and what it
> > doesn't work for) anyway. I'd expect it to be a target-independent
> > feature with a target
Am Montag, den 20.08.2018, 22:34 + schrieb Joseph Myers:
> On Mon, 20 Aug 2018, Uecker, Martin wrote:
>
> > This is a new version which adds proper changelog entries and
> > a test case (no actual code changes).
>
> Please include the overall description of a change in every version
> submit
On Mon, 20 Aug 2018, Uecker, Martin wrote:
> This is a new version which adds proper changelog entries and
> a test case (no actual code changes).
Please include the overall description of a change in every version
submitted. That is, the patch submission message should both include a
descript
