All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] libX11: patch configure.ac so a nios2 system is not seen as an os2 system.
Date: Fri, 5 Nov 2010 14:38:47 +0100	[thread overview]
Message-ID: <20101105133847.GP3440@jama> (raw)
In-Reply-To: <1288963608.3826.15.camel@mattotaupa>

On Fri, Nov 05, 2010 at 02:26:48PM +0100, Paul Menzel wrote:
> I agree.
> 
> > Then if it is in the inc file, it needs to be taken out again when the
> > next version comes.
> 
> Sorry, I did not make myself clear. My point was if you could put
> `configure.ac-nios2.patch` into `libX11/` or `files`.

better not to use files at all
http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-October/025673.html

diet-x11_1.1.5.bb libx11-trim_1.1.5.bb will find it ok in libx11* dir,
because of FILESPATHPKG .= ":libx11-${PV}:libx11" in libx11.inc

but even when it's the same file I would keep it in separate dirs,
because newer versions won't need it (hopefully) and then it will be
removed with older versions.

> > Hence it was put in the individual files.
> > 
> > BTW it looks like upstream might go for a slightly different patch.
> > I'll leave it to Martin to decide whether to go for that one or for
> > this one (he is on cc of the upstream correspondence).
> 
> Again, could you provide a link to that discussion.

http://lists.freedesktop.org/archives/xorg/2010-November/051731.html

Regards,

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



  parent reply	other threads:[~2010-11-05 13:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05 12:08 [PATCH] libX11: patch configure.ac so a nios2 system is not seen as an os2 system Frans Meulenbroeks
2010-11-05 12:51 ` Paul Menzel
2010-11-05 13:19   ` Frans Meulenbroeks
2010-11-05 13:26     ` Paul Menzel
2010-11-05 13:35       ` Frans Meulenbroeks
2010-11-05 13:38       ` Martin Jansa [this message]
2010-11-05 13:57         ` Paul Menzel
2010-11-05 15:36 ` Khem Raj
2010-11-05 17:23   ` Frans Meulenbroeks

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=20101105133847.GP3440@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.