All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Benjamin Calderon <benj.calderon@gmail.com>,
	Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH/next v3, 1/1] package/font-awesome: make it compatible with fontconfig
Date: Wed, 26 Jan 2022 13:26:08 +0100	[thread overview]
Message-ID: <87h79qisyn.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20211230152059.465b21a8@windsurf> (Thomas Petazzoni's message of "Thu, 30 Dec 2021 15:20:59 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > On Wed, 26 Feb 2020 10:09:39 +0100
 > Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

 >> This commit installs font-awesome in the standard fonts directory
 >> making it available systemwide.
 >> 
 >> Thanks to baruch for his technical critique.
 >> Signed-off-by: Benjamin Calderon <benj.calderon@gmail.com>
 >> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
 >> ---
 >> Changes v2 -> v3 (after review of Baruch Siach):
 >> - Create a symlink to avoid duplication

 > I have applied with a reworked commit log. That being said, I am not
 > sure it was really the "best" solution. It probably would be nicer to
 > install the fonts usable by fontconfig directly in /usr/share/fonts/,
 > keeping the rest in /usr/share/font-awesome/.

Committed to 2021.02.x and 2021.11.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-01-26 12:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26  9:09 [Buildroot] [PATCH/next v3, 1/1] package/font-awesome: make it compatible with fontconfig Fabrice Fontaine
2021-12-30 14:20 ` Thomas Petazzoni
2022-01-26 12:26   ` Peter Korsgaard [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=87h79qisyn.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=benj.calderon@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=thomas.petazzoni@bootlin.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.