From: Junqian Gordon Xu <xjqian@gmail.com>
To: Paul Sokolovsky <pmiscml@gmail.com>
Cc: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
angstrom-distro-devel@linuxtogo.org
Subject: Re: [Angstrom-devel] [RFC] Streamline the process of getting fixes from .dev --> feed
Date: Fri, 22 Feb 2008 01:34:34 -0500 [thread overview]
Message-ID: <47BE6CFA.2050609@gmail.com> (raw)
In-Reply-To: <20080221191327.63b6bc9a@widy.localdomain>
On 02/21/2008 12:13 PM, Paul Sokolovsky wrote:
> If I had, I'd probably do that too, even though I think that current
> process is still an RFC, subject for assessment how performant it is,
> and open for proposals for improvements. So, IMHO it would be to just
> open a usual wiki page for now.
http://linuxtogo.org/gowiki/Backport_from_dev_to_stable was created,
incorporating both Koen's and your inputs. Please help proof-read and
improve the format (I have to admit editing MoinMoin is just not my
thing...).
Regards
Gordon
prev parent reply other threads:[~2008-02-22 6:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47BCEECA.9000102@gmail.com>
2008-02-21 17:13 ` [Angstrom-devel] [RFC] Streamline the process of getting fixes from .dev --> feed Paul Sokolovsky
2008-02-22 6:34 ` Junqian Gordon Xu [this message]
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=47BE6CFA.2050609@gmail.com \
--to=xjqian@gmail.com \
--cc=angstrom-distro-devel@linuxtogo.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=pmiscml@gmail.com \
/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