From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Fix compilation of Openembedded on ppc64
Date: Tue, 09 Dec 2008 09:40:13 -0500 [thread overview]
Message-ID: <493E834D.1000508@balister.org> (raw)
In-Reply-To: <200812091307.25780.mickey@vanille-media.de>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
Michael 'Mickey' Lauer wrote:
> Am Tuesday 09 December 2008 11:43:30 schrieb Koen Kooi:
>> On 09-12-08 11:02, Michael 'Mickey' Lauer wrote:
>>> sent to org.oe.dev, thanks.
>> Could you please fix the commit message next time?
>
> Do you really think it's worth it? Not a strong opinion here, but this kind of
> destroys the elegant workflow with 'git am' and I think we should relax the
> policy for patches we receive by mail.
I haven't looked at the commit in question.
We should strive to have all the commit messages use the same format.
The occasional exception is OK, but I don't want to see specific
exceptions added to the policy. Also, if the message is really bad, it
should be fixed. If it is marginal, let it go, but remind the source to
do better next time.
Does this make sense?
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2008-12-09 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200812082037.03626.mb@bu3sch.de>
2008-12-09 10:02 ` [PATCH] Fix compilation of Openembedded on ppc64 Michael 'Mickey' Lauer
2008-12-09 10:43 ` Koen Kooi
2008-12-09 12:07 ` Michael 'Mickey' Lauer
2008-12-09 14:40 ` Philip Balister [this message]
[not found] ` <ghlp2t$kjl$1@ger.gmane.org>
[not found] ` <200812091903.00950.mb@bu3sch.de>
2008-12-09 18:11 ` Koen Kooi
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=493E834D.1000508@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.