From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Patches from patchwork queued in master-next for jenkins build
Date: Tue, 23 Sep 2014 19:46:02 +0200 [thread overview]
Message-ID: <20140923174602.GG25706@jama> (raw)
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
Hi,
all pending changes should be now in master-next, please verify that
I haven't missed any.
I've replied on few which didn't apply and will probably reply on few more
after the build verification (if failures are detected).
Especially after long windows like this, it would be really helpful if
more contributors update status of patches on patchwork. There was a lot
of superseeded patches I had to manually find and mark as such.
Also it's safer to send vN patch every time you update the branch with
your whole pull request, I've noticed it 2 times in the e-mails, so I've
fetched them from repo instead of patchwork, but patchwork is my primary
tool to track the changes, so PATCHvN sent in e-mail is safer way for me
to notice that I need to refresh some patch.
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
reply other threads:[~2014-09-23 17:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140923174602.GG25706@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.