All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "MacDonald, Joe" <Joe_MacDonald@mentor.com>
Cc: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: Before you ping some older patches
Date: Wed, 22 Feb 2017 23:51:12 +0100	[thread overview]
Message-ID: <20170222225112.GI3283@jama> (raw)
In-Reply-To: <2fd7334f-118c-44e2-9c17-a4e9f432d506@email.android.com>

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

On Wed, Feb 22, 2017 at 10:26:54PM +0000, MacDonald, Joe wrote:
> It might just be me, but the list in general has seemed a bit off since at least Monday. I have good reason to believe it has eaten at least two of my posts.

During OEDAM discussion I also had a feeling that both my replies to
"Splitting meta-oe?" thread were eaten by the ML gremlins, but both
appear at:
http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/thread.html
so that wasn't the case.

> On Feb 22, 2017 4:33 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> 1) Make sure they aren't already in master (or master-next), currently
> there is only one change in master-next:
> eb7979113 netcat-openbsd: fix implicit dependency on pkg-config
> 
> 2) Make sure there weren't some negative feedback comments on our change
> 
> 3) Make sure the change made it to patchwork, currently there is only
> one "open" change:
> https://patchwork.openembedded.org/patch/137499/
> 
> Be aware that the changes are usually daily marked as archived, when
> they are sorted to corresponding bundles and included in master-next
> branch for testing, as described here:
> http://www.openembedded.org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_project_on_patchwork
> 
> I'm writing this, because currently many changes are missing on patchwork,
> because of some unknown issue with it, see:
> http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/111467.html
> once this issue is resolved, please re-send missing changes.
> 
> Regards,
> 

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

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

  reply	other threads:[~2017-02-22 22:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 22:26 Before you ping some older patches MacDonald, Joe
2017-02-22 22:51 ` Martin Jansa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-02-22 23:09 MacDonald, Joe
2017-02-22 21:32 Martin Jansa
2017-02-22 23:06 ` Michael Halstead
2017-02-22 23:48   ` Martin Jansa
2017-02-23  0:08     ` Michael Halstead
2017-02-23  0:20     ` Derek Straka
2017-02-23  1:53     ` Martin Jansa
2017-02-23  1:58       ` Michael Halstead
2017-02-23  2:31         ` Michael Halstead

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=20170222225112.GI3283@jama \
    --to=martin.jansa@gmail.com \
    --cc=Joe_MacDonald@mentor.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.