Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>,
	 Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] libdrm: Upgrade to 2.4.58.
Date: Thu, 04 Dec 2014 12:00:13 -0600	[thread overview]
Message-ID: <5480A12D.1050701@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LY8s3e_Sdg47pOxktFGEemZpJANxGa=_Jx1x7FrP7Q8DQ@mail.gmail.com>

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

I made a patch v2 for this set,

https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=alimon/linux_intel_graphics_2014q3_v2

I'm testing it to send again.

Kind regards.

alimon

On 04/12/14 09:31, Burton, Ross wrote:
>
> On 4 December 2014 at 15:23, Nicolas Dechesne 
> <nicolas.dechesne@linaro.org <mailto:nicolas.dechesne@linaro.org>> wrote:
>
>     i didn't find any other package in -core where we really used a
>     PACKAGECONFIG for doc. so i would vote to simply do like we do in
>     every other packages, e.g.
>
>
> There is an effort by some to improve documentation generation, and 
> this is a fairly easy one to fix, but I'm easy either way.
>
>     By the way, this is not a new problem (sorry I know i reported it on
>     that thread ;-). This change for manpages was done in 2.4.42. So we
>     should not really block the update to 2.4.58, and if you agree on the
>     patch above, i can send it separately.
>
>
> As you've kindly tested it I'll merge a version with --disable unless 
> Anibal is going to go the extra mile.  :)
>
> Ross


[-- Attachment #2: Type: text/html, Size: 2829 bytes --]

  reply	other threads:[~2014-12-04 18:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01 22:36 [PATCH 0/3] Upgrades for comply Intel Graphics Stack Release 2014Q3 Aníbal Limón
2014-12-01 22:36 ` [PATCH 1/3] libdrm: Upgrade to 2.4.58 Aníbal Limón
2014-12-03 23:30   ` Burton, Ross
2014-12-04  7:14     ` Nicolas Dechesne
2014-12-04 14:40       ` Burton, Ross
2014-12-04 15:23         ` Nicolas Dechesne
2014-12-04 15:31           ` Burton, Ross
2014-12-04 18:00             ` Aníbal Limón [this message]
2014-12-01 22:36 ` [PATCH 2/3] mesa: Upgrade to 10.3.3 Aníbal Limón
2014-12-02 10:07   ` Nicolas Dechesne
2014-12-02 14:32     ` Aníbal Limón
2014-12-01 22:36 ` [PATCH 3/3] xorg-xserver: Upgrade to 1.16.2 Aníbal Limón
2014-12-02 14:28   ` Nicolas Dechesne
2014-12-02 14:50     ` Aníbal Limón
2014-12-02 15:16       ` Nicolas Dechesne
2014-12-02 15:36       ` Burton, Ross
2014-12-02 15:30 ` [PATCH 0/3] Upgrades for comply Intel Graphics Stack Release 2014Q3 Nicolas Dechesne

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=5480A12D.1050701@linux.intel.com \
    --to=anibal.limon@linux.intel.com \
    --cc=nicolas.dechesne@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox