From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Tom Zanussi <tom.zanussi@intel.com>
Cc: Maciek Borzecki <maciek.borzecki@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] wic: do not overwrite autogenerated /etc/fstab with original too early
Date: Fri, 25 Jul 2014 17:30:51 +0100 [thread overview]
Message-ID: <1406305851.27697.40.camel@ted> (raw)
In-Reply-To: <1406303860.6205.31.camel@empanada>
On Fri, 2014-07-25 at 10:57 -0500, Tom Zanussi wrote:
> On Fri, 2014-07-25 at 17:48 +0200, Maciek Borzecki wrote:
> > One question though. How do I get the patches into master? I'm not
> > @intel.com perhaps that's why I was a bit confused by the wiki
> > instructions. Would you be able to push all of these changes into your
> > tree, so that they would get to master with later merge?
> >
>
> They get pulled into master by Richard and Saul, no need to do anything
> else on your side (except ping them if you don't see them get merged in
> a reasonable timeframe ;-)
They're in FWIW.
Cheers,
Richard
next prev parent reply other threads:[~2014-07-25 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 15:48 [PATCH v2] wic: do not overwrite autogenerated /etc/fstab with original too early Maciek Borzecki
2014-07-25 15:57 ` Tom Zanussi
2014-07-25 16:30 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-25 17:18 Maciek Borzecki
2014-07-23 19:21 [PATCH 1/2] wic: original fstab restored " Tom Zanussi
2014-07-24 12:27 ` [PATCH v2] wic: do not overwrite autogenerated /etc/fstab with original " Maciej Borzecki
2014-07-25 0:49 ` Tom Zanussi
2014-07-25 15:00 ` Tom Zanussi
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=1406305851.27697.40.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=maciek.borzecki@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=tom.zanussi@intel.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 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.