Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Chris Elston <celston@katalix.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Recipe for util-linux-2.19.1
Date: Tue, 14 Jun 2011 15:53:10 +0100	[thread overview]
Message-ID: <1308063190.12359.43.camel@desktop.home> (raw)
In-Reply-To: <19457E2B-45A3-4A02-8BDB-58A538B6A1F6@dominion.thruhere.net>

> Chris, Saul updated to 2.19.1 two weeks ago:
> 
> http://cgit.openembedded.org/cgit.cgi/openembedded-core/commit/?id=596e6807826c34a4f93d7cb26052d1bd7a985201
> 
> It doesn't seem to have the vercmp change you mentioned, could you try to rebase your changes against that?

Thanks for pointing me at that.

I guess it's not required because that change doesn't maintain
compatibility with prior versions of util-linux, so no need to check the
versions.

Cheers,

Chris.





      reply	other threads:[~2011-06-14 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 14:10 [PATCH] Recipe for util-linux-2.19.1 Chris Elston
2011-06-14 14:24 ` Koen Kooi
2011-06-14 14:53   ` Chris Elston [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=1308063190.12359.43.camel@desktop.home \
    --to=celston@katalix.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox