From: Rob Woolley <rob.woolley@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 0/3] Identify existing configuration files
Date: Tue, 10 Mar 2015 11:37:32 -0400 [thread overview]
Message-ID: <54FF0FBC.3050806@windriver.com> (raw)
In-Reply-To: <CAJTo0LY-DwnvrtA0mfDTKnggkBZ491POJJVMTTap87koO+c4Fw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
Hi Ross,
Sure thing.
I applied them to a fresh clone of openembedded-core.git and pushed it
to the conffiles branch on github:
https://github.com/rcwoolley/openembedded-core/tree/conffiles
Regards,
Rob
On 03/10/2015 09:51 AM, Burton, Ross wrote:
> Hi Rob,
>
> On 9 March 2015 at 23:52, Rob Woolley <rob.woolley@windriver.com
> <mailto:rob.woolley@windriver.com>> wrote:
>
> Some package formats explicitly track which files are
> configuration files
> so that they are not overwritten on updates.
>
> This series explicitly identifies files that were already being
> packaged,
> but not known as configuration files.
>
>
> Do you have these patches in a branch? git am is claiming they're
> corrupted, so something must have happened to them in transit.
>
> Cheers,
> Ross
[-- Attachment #2: Type: text/html, Size: 2214 bytes --]
prev parent reply other threads:[~2015-03-10 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 23:52 [PATCH v2 0/3] Identify existing configuration files Rob Woolley
2015-03-09 23:52 ` [PATCH v2 1/3] nfs-utils: Install nfsmount.conf Rob Woolley
2015-03-09 23:52 ` [PATCH v2 2/3] nfs-utils: Identify CONFFILES Rob Woolley
2015-03-10 16:05 ` Burton, Ross
2015-03-10 17:14 ` Rob Woolley
2015-03-09 23:52 ` [PATCH v2 3/3] logrotate: " Rob Woolley
2015-03-10 13:51 ` [PATCH v2 0/3] Identify existing configuration files Burton, Ross
2015-03-10 15:37 ` Rob Woolley [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=54FF0FBC.3050806@windriver.com \
--to=rob.woolley@windriver.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.