From: Rod Whitby <rod@whitby.id.au>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Having trouble keeping track of the Patches?
Date: Sat, 14 Feb 2009 13:46:47 +1030 [thread overview]
Message-ID: <4996379F.50003@whitby.id.au> (raw)
In-Reply-To: <499570E4.1020503@balister.org>
Philip Balister wrote:
> Patches sent to the list are being tracked with patchwork now:
>
> http://patchwork.openembedded.org/project/openembedded/list/
>
> If you submit a patch, please update the flags as comments occur and
> consensus happens.
I've applied patch 22 to oe.dev, and have an account on patchwork - how
do I update it to identify that it has been applied?
-- Rod
next prev parent reply other threads:[~2009-02-14 3:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 13:08 Having trouble keeping track of the Patches? Philip Balister
2009-02-14 3:16 ` Rod Whitby [this message]
2009-02-14 4:00 ` Khem Raj
2009-02-14 8:42 ` Rolf Leggewie
2009-02-14 14:06 ` Philip Balister
2009-02-14 19:52 ` Rolf Leggewie
2009-02-14 20:17 ` Philip Balister
2009-02-15 14:36 ` Rolf Leggewie
2009-02-15 23:26 ` Michael 'Mickey' Lauer
2009-02-16 2:49 ` Philip Balister
2009-02-14 8:34 ` Koen Kooi
2009-02-14 14:04 ` 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=4996379F.50003@whitby.id.au \
--to=rod@whitby.id.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox