From: Leho Kraav <leho@kraav.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] epatch: splitting out common options from user-specific ones
Date: Fri, 20 Apr 2012 23:06:02 +0300 [thread overview]
Message-ID: <4F91C1AA.9080608@kraav.com> (raw)
In-Reply-To: <201204201559.39849.vapier@gentoo.org>
On 20.04.2012 22:59, Mike Frysinger wrote:
> i just committed it since no one responded. so sync up.
>
>> $ EPATCH_OPTS="--ignore-whitespace" emerge -va pf-sources
>
> that's not the intention. EPATCH_OPTS modification should be inside the
> ebuild.
I can't see how having this available could hurt anything. Am I blind?
next prev parent reply other threads:[~2012-04-20 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <iRHui-2kD-3@gated-at.bofh.it>
2012-04-20 19:38 ` [gentoo-dev] epatch: splitting out common options from user-specific ones Leho Kraav
2012-04-20 19:54 ` Leho Kraav
2012-04-20 19:59 ` Mike Frysinger
2012-04-20 20:06 ` Leho Kraav [this message]
2012-04-20 21:40 ` Mike Frysinger
2012-04-18 18:03 Mike Frysinger
2012-04-20 3:24 ` Mike Frysinger
2012-04-20 3:38 ` Mike Frysinger
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=4F91C1AA.9080608@kraav.com \
--to=leho@kraav.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=vapier@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