public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Henry Gebhardt <hsggebhardt@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Review for initial systemd.eclass
Date: Wed, 4 May 2011 15:56:32 +0200	[thread overview]
Message-ID: <20110504135632.GA2502@bimsstein> (raw)
In-Reply-To: <20110504125445.504d0ffd@pomiocik.lan>

On Wed, May 04, 2011 at 12:54:45PM +0200, Michał Górny wrote:
> On Sat, 30 Apr 2011 23:17:42 +0200
> Michał Górny <mgorny@gentoo.org> wrote:
> 
> > Here's the second version.

I think the "inherit multilib" line is no longer needed.

> I committed this version to gx86. All packages providing systemd units
> are free to use it now, yet I'm still open to comments.

Does this mean we can or should file bugs like [1] and [2] against
packages? I am in particular thinking of avahi, consolekit, and soon
networkmanager.


Thanks,

Henry

[1] https://bugs.gentoo.org/show_bug.cgi?id=365941
[2] https://bugs.gentoo.org/show_bug.cgi?id=365943



  reply	other threads:[~2011-05-04 13:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29  5:58 [gentoo-dev] Review for initial systemd.eclass Michał Górny
2011-04-30 21:17 ` Michał Górny
2011-05-04 10:54   ` Michał Górny
2011-05-04 13:56     ` Henry Gebhardt [this message]
2011-05-04 16:15       ` Michał Górny

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=20110504135632.GA2502@bimsstein \
    --to=hsggebhardt@googlemail.com \
    --cc=gentoo-dev@lists.gentoo.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