All of lore.kernel.org
 help / color / mirror / Atom feed
From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Cc: "Burton, Ross" <ross.burton-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 0/5] Remove /var/cache from volatiles directory
Date: Mon, 04 Feb 2013 19:25:11 +0100	[thread overview]
Message-ID: <lyvca89bso.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <CAJTo0LaBDWRhcf+kj_k6OrV0B0sE98Fnoe5+XAK4gOhPzZTgjw@mail.gmail.com> (Ross Burton's message of "Mon, 4 Feb 2013 17:51:05 +0000")

"Burton, Ross" <ross.burton-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
writes:

> The fontconfig cache is perfectly capable of generation at image
> creation time,

really? The cache files are architecture dependent and I am not aware of
a cross-fc-cache tool.



Enrico



  reply	other threads:[~2013-02-04 18:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04  9:26 [PATCH 0/5] Remove /var/cache from volatiles directory Laurentiu Palcu
2013-02-04  9:26 ` [PATCH 1/5] base-files: remove /var/cache from volatiles Laurentiu Palcu
2013-02-04  9:26 ` [PATCH 2/5] fs-perms: " Laurentiu Palcu
2013-02-04  9:26 ` [PATCH 3/5] initscripts: " Laurentiu Palcu
2013-02-04  9:26 ` [PATCH 4/5] systemd: " Laurentiu Palcu
2013-02-04  9:26 ` [PATCH 5/5] rpm: remove /var/volatiles/cache/rpm from the FILEs list Laurentiu Palcu
2013-02-04  9:46 ` [PATCH 0/5] Remove /var/cache from volatiles directory Mike Looijmans
2013-02-04 10:03   ` Laurentiu Palcu
2013-02-04 11:51     ` Richard Purdie
2013-02-04 17:47     ` Phil Blundell
2013-02-04 17:51       ` Burton, Ross
2013-02-04 18:25         ` Enrico Scholz [this message]
2013-02-04 19:36           ` Burton, Ross
2013-02-05  2:37 ` ChenQi
2013-02-05  9:56   ` Laurentiu Palcu
2013-02-05 20:50 ` 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=lyvca89bso.fsf@ensc-virt.intern.sigma-chemnitz.de \
    --to=enrico.scholz@sigma-chemnitz.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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.