From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: ml@communistcode.co.uk
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe][PATCH 1/3] latencytop: disable GTK and remove gtk+ dependacy
Date: Fri, 26 Oct 2012 13:49 +0100 [thread overview]
Message-ID: <2123894.VsbK2PYknT@helios> (raw)
In-Reply-To: <508A83F0.7040603@communistcode.co.uk>
On Friday 26 October 2012 13:37:04 Jack Mitchell wrote:
> So you're saying I should do:
>
> git send-email -3 --no-chain-reply-to --cover-letter --to
> openembedded-core@lists.openembedded.org --subject-prefix=oe][PATCH
>
> And also remove the '---' from my commit message on patch 1?
I don't use this method myself (for >1 patch I tend to use the create-pull-
request / send-pull-request scripts, but that assumes you have somewhere to
push a branch); however that looks like it should be the right thing to do.
> I think [1] should be updated for a few more use cases e.g. multiple
> patches.
> [1] http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
Unfortunately like most of the pages on the OE wiki this is out-of-date.
Richard and I are going to try to set some time aside at ELCE to update the
wiki or at the very least mark outdated information; hopefully we can convince
others to join in as well.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-10-26 13:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 11:54 [oe][PATCH 1/3] latencytop: disable GTK and remove gtk+ dependacy Jack Mitchell
2012-10-26 11:54 ` [oe][PATCH 2/3] packagegroup-core-tools-profile: include sysprof only if x11 is distro feature Jack Mitchell
2012-10-26 11:54 ` [oe][PATCH 3/3] babeltrace: fix depends Jack Mitchell
2012-10-26 12:28 ` [oe][PATCH 1/3] latencytop: disable GTK and remove gtk+ dependacy Paul Eggleton
2012-10-26 12:35 ` Jack Mitchell
2012-10-26 12:37 ` Jack Mitchell
2012-10-26 12:49 ` Paul Eggleton [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=2123894.VsbK2PYknT@helios \
--to=paul.eggleton@linux.intel.com \
--cc=ml@communistcode.co.uk \
--cc=openembedded-core@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.