All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jens Rehsack <rehsack@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Update rrdtool from 1.4.8 to 1.5.3
Date: Mon, 13 Jul 2015 10:07:37 +0100	[thread overview]
Message-ID: <1436778457.3310.38.camel@linuxfoundation.org> (raw)
In-Reply-To: <635A9611-7B0D-4FB0-A643-88ACFAEE4C27@gmail.com>

On Mon, 2015-07-13 at 09:57 +0200, Jens Rehsack wrote:
> > Am 10.07.2015 um 21:50 schrieb Burton, Ross <ross.burton@intel.com>:
> > 
> > 
> > On 9 July 2015 at 17:38, Jens Rehsack <rehsack@gmail.com> wrote:
> > here is an update patch for meta-oe/recipes-extended/rrdtool:
> > https://github.com/rehsack/meta-openembedded/commit/6ed5b4489beb1233bd4b3c9f73064e973eeef2ad
> > 
> > Please send the actual patch instead of a link to the patch, and meta-oe patches go to openembedded-devel@ not -core@.
> 
> I was told by RP that sending patches via GitHub is fine. Unfortunately that's the best I can do.
> When it's clear how to submit patches, I'll go ahead to oe-devel@

Not sure I said github was ok. What I perhaps would have said is that
posting a link to such patches was better than not having anything at
all. There are some good improvements in there for perl and as you know,
our perl skills are a bit lacking :).

Our commit process is patches on the mailing list for review. If you
can't help with that, it means someone else will have to step up and do
that piece. Its then going to come down to how good the patches are as
to whether anyone does.

As I have said, I'd much rather know about them and have the option
rather than not know about them at all though.

Cheers,

Richard





  reply	other threads:[~2015-07-13  9:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 16:38 Update rrdtool from 1.4.8 to 1.5.3 Jens Rehsack
2015-07-10 19:50 ` Burton, Ross
2015-07-13  7:57   ` Jens Rehsack
2015-07-13  9:07     ` Richard Purdie [this message]
2015-07-13  9:54       ` Jens Rehsack

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=1436778457.3310.38.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rehsack@gmail.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.