From: "Michael 'Mickey' Lauer" <mickey@vanille-media.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Reverting recent openmoko commit
Date: Mon, 27 Oct 2008 14:03:09 +0100 [thread overview]
Message-ID: <200810271403.09864.mickey@vanille-media.de> (raw)
In-Reply-To: <200810271345.22194.zecke@selfish.org>
> Where from here?
> - I will merge yesterday's work again as is?
Yes.
> - I will ask our OM developers to use a different style in the commit
> message (even if this is not mandated) to not use braces but colons. And
> yes I think I asked them to use [] as I'm used to this from various other
> projects, I will ask them to change and change it myself.
Sounds good. Again, my take on this is: These policies are guidelines, not
strict requirements. If we decide otherwise, we need to have restrictive
commit hooks or switch over to a completely different model of working
together.
--
:M:
next prev parent reply other threads:[~2008-10-27 13:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 15:06 Reverting recent openmoko commit Koen Kooi
2008-10-26 15:39 ` Michael 'Mickey' Lauer
2008-10-27 9:10 ` Phil Blundell
2008-10-27 10:37 ` Philip Balister
2008-10-27 12:45 ` Holger Freyther
2008-10-27 13:03 ` Michael 'Mickey' Lauer [this message]
2008-10-27 16:09 ` Philip Balister
2008-10-27 13:12 ` Michael Krelin
2008-10-27 10:39 ` Philip Balister
2008-10-27 11:13 ` Michael Krelin
2008-10-27 11:30 ` Policies vs. Guidelines vs. Requirements (was: Reverting recent openmoko commit) Michael 'Mickey' Lauer
2008-10-27 11:46 ` Policies vs. Guidelines vs. Requirements Michael Krelin
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=200810271403.09864.mickey@vanille-media.de \
--to=mickey@vanille-media.de \
--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.