From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] site/arm-common: alignment values for guin32, guin64 and unsigned long
Date: Thu, 03 May 2012 07:07:41 -0700 [thread overview]
Message-ID: <4FA2912D.4070305@gmail.com> (raw)
In-Reply-To: <1336052808.30113.116.camel@ted>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/03/2012 06:46 AM, Richard Purdie wrote:
> I should also note that there is a wider problem here I'm
> complaining about. The glib issue is actually less of a concern.
>
> People keep sending patches without sensible descriptions in the
> commit message. I think I've made some comments on list to Saul
> about this to pick on someone in particular. The last set of
> patches from Khem contains one which removed pretty much the whole
> qemu patch set from the git version with no explanation in the
> commit message.
OK provide that feedback to the patch. I will improve on it. Are you
talking about below commit. I did mention patches are not forward ported
qemu-git: Move to tip of git
There are a lot of armv7 and sh4 fixes that its worth moving to latest
version. The patch forward porting can happen later.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
>
> No, its not going in and I find it a a bit of an insult that I'm
> being expected to read the diffs, notice these changes and spent
> time replying to the patch with a nicely worded rejection email. I
> might just start replying "no".
>
> So what I'm asking is that people think about the changes they
> submit and try and help me, not use patch submission as a sounding
> board and not to hope I don't spot something.
>
> To scale this project we need to develop trust relationships with
> people taking ownership of areas of the codebase. I consider Mark
> Hatle to "own" most things rpm for example. To scale we need to do
> more of this but trust is important. If some people don't want to
> do this and just contribute things when they can which interest
> them, that is fine but we are going to reach a point where we have
> to take longer to test and take such changes.
>
> Cheers,
>
> Richard
>
>
>
> _______________________________________________ Openembedded-core
> mailing list Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+ikS0ACgkQuwUzVZGdMxSK0wCdHTtEilAecZpvXkbd0Mak2LPw
NgIAn36cIeZ2fHbC85OFKXPrEkOsbU0q
=uyc9
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-05-03 14:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 13:59 [PATCH 0/2] glib-2.0 another upgrade Martin Jansa
2012-05-02 13:59 ` [PATCH 1/2] site/arm-common: alignment values for guin32, guin64 and unsigned long Martin Jansa
2012-05-02 14:09 ` Martin Jansa
2012-05-02 21:08 ` Khem Raj
2012-05-03 5:38 ` Martin Jansa
2012-05-03 5:44 ` Khem Raj
2012-05-03 5:46 ` Martin Jansa
2012-05-03 8:55 ` Richard Purdie
2012-05-03 9:29 ` Martin Jansa
2012-05-03 13:29 ` Richard Purdie
2012-05-03 13:46 ` Richard Purdie
2012-05-03 14:07 ` Khem Raj [this message]
2012-05-03 14:41 ` Martin Jansa
2012-05-03 14:50 ` Khem Raj
2012-05-02 13:59 ` [PATCH 2/2] glib-2.0: upgrade to 2.32.2 Martin Jansa
[not found] ` <cover.1335969047.git.Martin.Jansa@gmail.com>
2012-05-02 14:32 ` [PATCH 3/4] qt-4.8.1: fix creating /include directory in build host root Martin Jansa
2012-05-02 14:32 ` [PATCH 4/4] site/ix86-common, site/x86_64-linux: alignment values for guin32, guin64 and unsigned long Martin Jansa
[not found] ` <cover.1336023730.git.Martin.Jansa@gmail.com>
2012-05-03 5:42 ` [PATCH 5/5] gtk-engines: fix build with glib-2.32 Martin Jansa
2012-05-03 20:24 ` Saul Wold
2012-05-07 16:17 ` [PATCH 0/2] glib-2.0 another upgrade Saul Wold
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=4FA2912D.4070305@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox