All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Mikko.Rapeli@bmw.de>
To: <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] sanity.bbclass: check SSTATE_DIR, DL_DIR and *MIRROR for broken symlinks
Date: Mon, 10 Aug 2015 17:02:47 +0000	[thread overview]
Message-ID: <20150810170250.GJ6102@loska> (raw)
In-Reply-To: <CAJTo0LaNdbbS++REvbB5Gw-FQ736emDpwCH0G-hzZrxZCs9QFA@mail.gmail.com>

On Mon, Aug 10, 2015 at 05:35:27PM +0100, Burton, Ross wrote:
> On 10 August 2015 at 09:18, <Mikko.Rapeli@bmw.de> wrote:
> 
> > So currently patch testing and review queues are full.
> >
> > Should I file bugzilla tickets with links to patches like this or
> > are the mailing list contributions tracked via patchwork or something?
> >
> > If small changes like this are not getting merged, then I don't have
> > confidence
> > in pushing bigger ones back upstream.
> >
> 
> There's been slow acceptance of patches on master recently, mainly due to a
> focus on making the autobuilder do green runs reliably.  To compound that,
> I've just returned from a week off and Richard was travelling last week and
> is still travelling this week.
> 
> That said, master-next is almost 50 commits ahead of master and will be
> merged soon, and I've just queued this into my testing branch.  Stuff is
> flowing, just slowly.

Thanks for the update. I was just wondering if there's anything I could/should
do as a drive-by-contributor.

-Mikko

      reply	other threads:[~2015-08-10 17:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31  9:00 [PATCH] sanity.bbclass: check SSTATE_DIR, DL_DIR and *MIRROR for broken symlinks Mikko Rapeli
2015-08-10  8:18 ` Mikko.Rapeli
2015-08-10  9:10   ` Mike Looijmans
2015-08-10 11:48     ` Mikko.Rapeli
2015-08-10 14:00       ` [PATCH v2] " Mikko Rapeli
2015-08-10 16:35   ` [PATCH] " Burton, Ross
2015-08-10 17:02     ` Mikko.Rapeli [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=20150810170250.GJ6102@loska \
    --to=mikko.rapeli@bmw.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@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.