From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] xattr wrapper for install, bug #465000
Date: Mon, 27 Jan 2014 23:36:33 -0500 [thread overview]
Message-ID: <2540083.UCf25BPGXR@vapier> (raw)
In-Reply-To: <52E666F6.8020102@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 266 bytes --]
On Monday, January 27, 2014 15:02:30 vivo75@gmail.com wrote:
> patch install from coreutils (and then upstream changes) is not an option?
that route is being pursued independently. we already have a wrapper and will
have one for the foreseeable future.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-28 4:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 22:53 [gentoo-portage-dev] xattr wrapper for install, bug #465000 Anthony G. Basile
2014-01-27 14:02 ` vivo75
2014-01-28 4:36 ` Mike Frysinger [this message]
2014-01-29 16:33 ` Anthony G. Basile
2014-01-29 23:50 ` Francesco R.
2014-01-31 4:43 ` Mike Frysinger
2014-01-31 4:53 ` Brian Dolbec
2014-01-31 19:55 ` Greg Turner
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=2540083.UCf25BPGXR@vapier \
--to=vapier@gentoo.org \
--cc=gentoo-portage-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