On 13.06.2018 00:54, Robert Elz wrote:
> Date:Tue, 12 Jun 2018 19:52:43 +0200
> From:Kamil Rytarowski
> Message-ID: <90519caf-289c-b4d3-7ebc-d14d4efc9...@gmx.com>
>
> | I will try to meet the expectations in commit messages for *San fixes.
>
> That would be good
Date:Tue, 12 Jun 2018 19:52:43 +0200
From:Kamil Rytarowski
Message-ID: <90519caf-289c-b4d3-7ebc-d14d4efc9...@gmx.com>
| I will try to meet the expectations in commit messages for *San fixes.
That would be good (and not just those, unless the board required it,
On 12.06.2018 15:52, Joerg Sonnenberger wrote:
> On Tue, Jun 12, 2018 at 02:35:40PM +0200, Kamil Rytarowski wrote:
>> On 12.06.2018 14:24, Joerg Sonnenberger wrote:
>>> That's missing the point. A short description of why the specific
>>> undefined behavior is seen is useful. Pasting random
On Tue, Jun 12, 2018 at 02:35:40PM +0200, Kamil Rytarowski wrote:
> On 12.06.2018 14:24, Joerg Sonnenberger wrote:
> > That's missing the point. A short description of why the specific
> > undefined behavior is seen is useful. Pasting random program output is
> > not.
> >
> > Joerg
> >
>
>
On 12.06.2018 14:24, Joerg Sonnenberger wrote:
> On Tue, Jun 12, 2018 at 12:00:01PM +0200, Kamil Rytarowski wrote:
>> On 12.06.2018 11:51, matthew green wrote:
On 12.06.2018 10:28, Kamil Rytarowski wrote:
> On 12.06.2018 09:04, Martin Husemann wrote:
>> On Tue, Jun 12, 2018 at
On 12.06.2018 11:51, matthew green wrote:
>> On 12.06.2018 10:28, Kamil Rytarowski wrote:
>>> On 12.06.2018 09:04, Martin Husemann wrote:
On Tue, Jun 12, 2018 at 05:47:35AM +0300, Valery Ushakov wrote:
> To sum it up, out of 30+ lines of the commit message, the relevant
> information
>On 12.06.2018 10:28, Kamil Rytarowski wrote:
>> On 12.06.2018 09:04, Martin Husemann wrote:
>>> On Tue, Jun 12, 2018 at 05:47:35AM +0300, Valery Ushakov wrote:
To sum it up, out of 30+ lines of the commit message, the relevant
information is contained only in (part of) one line.
>>>
>>>
On 12.06.2018 10:28, Kamil Rytarowski wrote:
> On 12.06.2018 09:04, Martin Husemann wrote:
>> On Tue, Jun 12, 2018 at 05:47:35AM +0300, Valery Ushakov wrote:
>>> To sum it up, out of 30+ lines of the commit message, the relevant
>>> information is contained only in (part of) one line.
>>
>> FWIW,
On 12.06.2018 09:04, Martin Husemann wrote:
> On Tue, Jun 12, 2018 at 05:47:35AM +0300, Valery Ushakov wrote:
>> To sum it up, out of 30+ lines of the commit message, the relevant
>> information is contained only in (part of) one line.
>
> FWIW, I fully agree with uwe here.
>
> Martin
>
I find
On Tue, Jun 12, 2018 at 05:47:35AM +0300, Valery Ushakov wrote:
> To sum it up, out of 30+ lines of the commit message, the relevant
> information is contained only in (part of) one line.
FWIW, I fully agree with uwe here.
Martin
On Mon, Jun 11, 2018 at 21:59:19 -0400, John Hawkinson wrote:
> Valery Ushakov wrote on Tue, 12 Jun 2018
> at 04:50:36 +0300 in <20180612015036.ge15...@pony.stderr.spb.ru>:
>
> > Please, can you keep your commit messages to the point?
> >
> > "Fix unportable left shift"
> >
> > is probably
Valery Ushakov wrote on Tue, 12 Jun 2018
at 04:50:36 +0300 in <20180612015036.ge15...@pony.stderr.spb.ru>:
> Please, can you keep your commit messages to the point?
>
> "Fix unportable left shift"
>
> is probably a good enough summary. You don't have to paste the test
> suite results and
Please, can you keep your commit messages to the point?
"Fix unportable left shift"
is probably a good enough summary. You don't have to paste the test
suite results and the actual diffs in free form as well.
On Tue, Jun 12, 2018 at 00:42:17 +, Kamil Rytarowski wrote:
> Log Message:
>
13 matches
Mail list logo
