Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: McClintock Matthew-B29882 <B29882@freescale.com>,
	bitbake-devel <bitbake-devel@lists.openembedded.org>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [bitbake-devel] should we switch off patchwork for oe-core and bitbake projects
Date: Wed, 1 Feb 2012 19:19:09 +0100	[thread overview]
Message-ID: <20120201181909.GC6969@jama.jama.net> (raw)
In-Reply-To: <CAMKF1sqkdApUR9YPamhtxtUHoanHZ5Sxp8ggUnp8PS0v_qPPgg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 979 bytes --]

On Wed, Feb 01, 2012 at 10:07:14AM -0800, Khem Raj wrote:
> On Wed, Feb 1, 2012 at 9:51 AM, McClintock Matthew-B29882
> <B29882@freescale.com> wrote:
> > I'm saying leave it there even if its not maintained. I can still go search
> > for patches sent by me or other specific people.
> 
> thats what mailing list archives are for.

is there something like
oe/contrib/patchwork/pw-am.sh
for some mailing list archive?

When I see some interesting patch in ML, easiest way for me to get it to
development branch is to open patchwork web (from any computer) and then
call pw-am.sh NUMBER in screen session on my development workstation.

Even when reading mail in mutt on the same machine it's easier for me to
use pw-am.sh to get that patch to my chroot for OE builds.

And that git hook marking them as applied works very well.. so usually I
just have to mark cover letters as applied.

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2012-02-01 18:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 16:04 should we switch off patchwork for oe-core and bitbake projects Khem Raj
2012-02-01 16:12 ` [bitbake-devel] " Martin Jansa
2012-02-01 17:07 ` McClintock Matthew-B29882
2012-02-01 17:48   ` Otavio Salvador
2012-02-01 17:51     ` McClintock Matthew-B29882
2012-02-01 18:07       ` Khem Raj
2012-02-01 18:19         ` Martin Jansa [this message]
2012-02-01 18:56           ` McClintock Matthew-B29882
2012-02-01 19:36           ` Khem Raj
2012-02-01 20:39           ` Denys Dmytriyenko

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=20120201181909.GC6969@jama.jama.net \
    --to=martin.jansa@gmail.com \
    --cc=B29882@freescale.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@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