All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <joshua.lock@collabora.co.uk>
To: Bryan Evenson <bevenson@melinkcorp.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 00/70] Proposed changes for fido
Date: Mon, 11 May 2015 16:07:31 +0100	[thread overview]
Message-ID: <1431356851.3086.12.camel@collabora.co.uk> (raw)
In-Reply-To: <BN3PR0501MB1090244F8445D0795045EC21BBDB0@BN3PR0501MB1090.namprd05.prod.outlook.com>

Hi Bryan,

On Mon, 2015-05-11 at 12:40 +0000, Bryan Evenson wrote:
> > Bryan Evenson (1):
> >   util-linux: Add lastb to alternatives
> 
> There is a refined version of this patch available that was 
> submitted to the mailing list here: 
> http://lists.openembedded.org/pipermail/openembedded-core/2015
> -April/104132.html.  It uses PACKAGECONFIG to remove last, lastb and 
> the man pages for last and lastb from the util-linux build if 'last' 
> is not in PACKAGECONFIG.  It also adds 'last' to PACKAGECONFIG by 
> default which mimics previous behavior.  I'm still a little unclear 
> on the patch approval process, so I assume the updated patch would 
> need to be accepted into master before being backported into fido?

Unless the patch is specific to the stable branch we only pull in
changes into a stable branch once they have been reviewed and accepted
into the master branch.

Is this change valuable without the refined patch? Or should I pull it
until I can merge both?

Thanks,

Joshua


  reply	other threads:[~2015-05-11 15:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11  8:40 [PATCH 00/70] Proposed changes for fido Joshua Lock
2015-05-11  8:51 ` Robert Yang
2015-05-11 15:07   ` Joshua Lock
2015-05-11 12:40 ` Bryan Evenson
2015-05-11 15:07   ` Joshua Lock [this message]
2015-05-11 15:46     ` Bryan Evenson

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=1431356851.3086.12.camel@collabora.co.uk \
    --to=joshua.lock@collabora.co.uk \
    --cc=bevenson@melinkcorp.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 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.