public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Libvirt hard dependencies [2]
Date: Tue, 29 Mar 2016 21:58:53 +0100	[thread overview]
Message-ID: <1459285133.30749.225.camel@ipfire.org> (raw)
In-Reply-To: <1459281126-767-1-git-send-email-jonatan.schlag@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 735 bytes --]

This looks good.

I would still like to delay the merge until the remaining parts are ready
because this is useless until then.

Best,
-Michael

On Tue, 2016-03-29 at 21:52 +0200, Jonatan Schlag wrote:
> Hi,
> this is the second patch series for the hard dependencies of Libvirt.
> The only difference between this series and the previous one ist that the
> rootfiles of all build dependencies are moved into config/rootfiles/common. 
> Everything should build now.
> 
> @Michael Tremer :
> I will send a patch series for dmidecode standalone because there are
> some  patches which are recommended by the project for dmidecode 3.
> These patches would blow up this patch series to much. 
> 
> Regards Jonatan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2016-03-29 20:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 19:52 Jonatan Schlag
2016-03-29 19:52 ` [PATCH 1/4] New package util-macros (required by libpciaccess (only for build)) Jonatan Schlag
2016-03-29 19:52 ` [PATCH 2/4] New package libpciaccess (required by libvirt) Jonatan Schlag
2016-03-29 19:52 ` [PATCH 3/4] New package libyajl " Jonatan Schlag
2016-03-29 19:52 ` [PATCH 4/4] Add all new packages (util-macros, libpciaccess, libyajl) to make.sh Jonatan Schlag
2016-03-29 20:58 ` Michael Tremer [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=1459285133.30749.225.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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