All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [CONSOLIDATED PULL 00/18] Final Review Pending
Date: Mon, 15 Jul 2013 11:15:46 +0100	[thread overview]
Message-ID: <2367199.H1kLtvBBbA@helios> (raw)
In-Reply-To: <CAJTo0LZcqo1ND1CTE91MU4jr0ovBggdhE2iXab1faCC+C1fROA@mail.gmail.com>

On Monday 15 July 2013 10:57:23 Burton, Ross wrote:
> On 15 July 2013 10:24, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
> >> Hongxu Jia (5):
> >>   pmount: add version 0.9.23
> >>   udev-extraconf:fix xuser write to usb storage failed
> >>   udev: fix invoking pmount failed based on sysvinit
> >>   pmount: allow users in disk group to perform pmount/pumount
> >>   xuser-account: add xuser to disk group
> > 
> > I have some reservations about these changes. pmount is obsolete
> > according to its author:
> > 
> > https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2011-February/01242
> > 1.html
> > 
> > I appreciate it may solve the problem we're trying to solve but we need
> > to be pretty confident about pulling this in before we do so since we'll
> > likely be supporting it ourselves.
> 
> Agreed.  pmount solves a problem but it's unmaintained and going
> forwards we need to sort out our at_console/polkit/etc story, and this
> is part of it.  I'd been meaning to take a good look at this series
> today, can we pull it for now?

Depends what you mean by "pull"... ?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-07-15 10:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15  7:23 [CONSOLIDATED PULL 00/18] Final Review Pending Saul Wold
2013-07-15  9:24 ` Paul Eggleton
2013-07-15  9:57   ` Burton, Ross
2013-07-15 10:15     ` Paul Eggleton [this message]
2013-07-15 11:23       ` Burton, Ross
2013-07-15 11:42   ` Hongxu Jia
2013-07-15 14:36   ` Saul Wold

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=2367199.H1kLtvBBbA@helios \
    --to=paul.eggleton@linux.intel.com \
    --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 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.