From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: patch queue/patchwork: How should states be used? (was: update canutils to current version)
Date: Sat, 14 Aug 2010 10:21:22 +0200 [thread overview]
Message-ID: <20100814082121.GF10076@jama> (raw)
In-Reply-To: <AANLkTin28kSQZTgWHd_DsXcqeANKfBcg3+NLaOP74kaD@mail.gmail.com>
On Sat, Aug 14, 2010 at 09:59:59AM +0200, Frans Meulenbroeks wrote:
> review patch. if ok and it is a simple patch
> download patch from patchwork in mbox fmt
> git am patch
> bitbake recipe
> if ok, git push.
check contrib/patchwork/pw-am.sh to simplify steps 2 and 3.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2010-08-14 8:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 5:30 update canutils to current version Vitus Jensen
2010-08-13 5:30 ` [PATCH 1/3] canutils: remove old version 4.0.4 Vitus Jensen
2010-08-13 6:31 ` Frans Meulenbroeks
2010-08-13 5:30 ` [PATCH 2/3] libsocketcan: remove old version 0.0.7 Vitus Jensen
2010-08-13 6:32 ` Frans Meulenbroeks
2010-08-13 5:30 ` [PATCH 3/3] canutils: update to version 4.0.6 Vitus Jensen
2010-08-13 6:33 ` Frans Meulenbroeks
2010-08-13 8:44 ` update canutils to current version Vitus Jensen
2010-08-13 9:24 ` Frans Meulenbroeks
2010-08-13 9:59 ` Vitus Jensen
2010-08-13 10:23 ` Frans Meulenbroeks
2010-08-13 14:40 ` Khem Raj
2010-08-13 21:01 ` Vitus Jensen
2010-08-13 21:27 ` patch queue/patchwork: How should states be used? (was: update canutils to current version) Paul Menzel
2010-08-14 7:59 ` Frans Meulenbroeks
2010-08-14 8:21 ` Martin Jansa [this message]
2010-09-07 20:10 ` patch queue/patchwork: How should states be used? Vitus Jensen
2010-09-08 6:00 ` Frans Meulenbroeks
2010-08-14 7:10 ` update canutils to current version Frans Meulenbroeks
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=20100814082121.GF10076@jama \
--to=martin.jansa@gmail.com \
--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.