From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Cleaning out patchwork queue
Date: Tue, 21 Apr 2009 22:50:57 +0200 [thread overview]
Message-ID: <gslbjh$pvu$1@ger.gmane.org> (raw)
In-Reply-To: <200904220025.33983.khimov@altell.ru>
On 21-04-09 22:25, Roman I Khimov wrote:
> On Tuesday 21 April 2009 22:31:20 Koen Kooi wrote:
>> If you have outstanding patches and no commit access (hi Roman!) ping
>> them again on this list and pester people in IRC to apply them.
>
> Well, don't like to pester people in general, but there you go.
Could you have a look at your patches listed here:
http://patchwork.openembedded.org/project/openembedded/list/?state=3
some are still using packages instead of recipes and they seem to fail
on checksums.ini since git can't merge its way out of a wet paper bag.
Only sending patches for the recipes and one big patch for checksums.ini
would acceptable to me as well.
regards,
Koen
next prev parent reply other threads:[~2009-04-21 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 18:31 Cleaning out patchwork queue Koen Kooi
2009-04-21 20:25 ` Roman I Khimov
2009-04-21 20:50 ` Koen Kooi [this message]
2009-04-22 5:28 ` Roman I Khimov
2009-04-21 20:51 ` Philip Balister
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='gslbjh$pvu$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.