Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: "José Bollo" <jobol@nonadev.net>
Cc: "José Bollo" <jose.bollo@iot.bzh>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] shadow: 'useradd' copies root's extended attributes
Date: Thu, 09 Mar 2017 18:18:05 +0100	[thread overview]
Message-ID: <1489079885.7785.371.camel@intel.com> (raw)
In-Reply-To: <20170309174815.056bc5a2@d-jobol.iot.bzh>

On Thu, 2017-03-09 at 17:48 +0100, José Bollo wrote:
> On Thu, 09 Mar 2017 17:07:54 +0100
> Patrick Ohly <patrick.ohly@intel.com> wrote:
> > Can't you reorder and rebase the patches so that this
> > 0001-useradd.c-create-parent-directories-when-necessary.patch applies
> > on top of the patch which was submitted upstream?
> 
> I agree that it would be better to reorder. Better but less
> conservative because an existing patch must be upgraded.

If upstream merges the proposed patch, then rebasing will be inevitable
at some point, so we might as well do the cleaner solution now, even if
the diff becomes larger.

> > "devtool modify shadow-native" might be useful for that. "git rebase
> > -i" in workspace/sources/shadow-native", then finish with "devtool
> > update-recipe shadow-native". I haven't tried whether "update-recipe"
> > handles re-ordering patches. If it doesn't, just fix it manually.
> 
> I'll do and propose the new version soon.

Thanks!

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





  reply	other threads:[~2017-03-09 17:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09 14:07 [PATCH] shadow: 'useradd' copies root's extended attributes jobol
2017-03-09 16:07 ` Patrick Ohly
2017-03-09 16:48   ` José Bollo
2017-03-09 17:18     ` Patrick Ohly [this message]
2017-03-15  8:04       ` José Bollo
2018-01-04  9:28         ` wenzong fan
2018-01-04  9:31           ` wenzong fan
2018-01-04 10:18           ` José Bollo
2018-01-04 10:41             ` Patrick Ohly
2018-01-04 11:39               ` wenzong fan
2018-01-04 11:50                 ` Patrick Ohly
2018-01-05  1:07                   ` Fan, Wenzong
2018-01-09 17:01                     ` Patrick Ohly
2018-01-10  9:50                       ` wenzong fan
2018-01-15 14:33                         ` José Bollo
2018-01-15 16:58                           ` Patrick Ohly
2018-01-16  2:53                           ` wenzong fan
2018-01-09 17:51               ` Mark Hatle
2018-01-10 11:15                 ` Patrick Ohly
  -- strict thread matches above, loose matches on Subject: below --
2017-03-13  9:57 jobol

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=1489079885.7785.371.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=jobol@nonadev.net \
    --cc=jose.bollo@iot.bzh \
    --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