-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/19/15 06:10, Mike Gilbert wrote:
On Wed, Feb 18, 2015 at 7:08 PM, Patrick Lauer patr...@gentoo.org
wrote:
On Wednesday 18 February 2015 18:43:59 hasufell wrote:
Is there a communication problem?
I don't remember getting either: * a bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/19/2015 09:57 AM, Markos Chandras wrote:
On 02/19/15 06:10, Mike Gilbert wrote:
On Wed, Feb 18, 2015 at 7:08 PM, Patrick Lauer
patr...@gentoo.org wrote:
On Wednesday 18 February 2015 18:43:59 hasufell wrote:
..
What saddens me the
On Thu, 19 Feb 2015 14:14:37 -0500
Mike Frysinger vap...@gentoo.org wrote:
pro: improved security in daemons (often network)
con: some packages might pull in libseccomp (~250KB)
there shouldn't be measurable runtime overhead here as the filtering
is done by a JIT in the kernel itself. if
On Wed, 18 Feb 2015 19:58:29 +0800
Ben de Groot yng...@gentoo.org wrote:
The attached patch proposes two helper functions to be added to
qmake-utils.eclass. These functions echo the correct directory where
qt binaries such as moc and lrelease are located. They can be used in
ebuilds when such
On Thu, Feb 19, 2015 at 1:30 PM, hasufell hasuf...@gentoo.org wrote:
* teams in gentoo are a mess, because they mostly work without much
communication and are sort of a badge for people to randomly touch
ebuilds they are not familiar with
So, this is also something I don't like about our
On Thu, Feb 19, 2015 at 2:06 PM, Andrew Savchenko birc...@gentoo.org wrote:
Please explain this proposal in more detail. If code review is
supposed to be mandatory for each commit, this will effectively stop
development. If it is supposed to be used as an auxiliary but
not mandatory tool, e.g.
On 02/19/2015 03:43 PM, Rich Freeman wrote:
I believe the proposal was for this to be purely optional. As such I
completely support it (though I think we should consider just using
the -dev-help list if it is still functional).
Purely optional.
To correct my original email, the mailing
On Thursday 19 February 2015 12:31:27 Alexis Ballier wrote:
On Wed, 18 Feb 2015 22:48:27 +0100
Michał Górny mgo...@gentoo.org wrote:
Dnia 2015-02-18, o godz. 16:11:53
Mike Frysinger (vapier) vap...@gentoo.org napisał(a):
vapier 15/02/18 16:11:53
Modified:
On Wed, 18 Feb 2015 22:48:27 +0100
Michał Górny mgo...@gentoo.org wrote:
Dnia 2015-02-18, o godz. 16:11:53
Mike Frysinger (vapier) vap...@gentoo.org napisał(a):
vapier 15/02/18 16:11:53
Modified: fcaps.eclass
Log:
clarify USE=filecaps intention #540430
On Thursday 19 February 2015 10:07:30 Kristian Fiskerstrand wrote:
On 02/19/2015 09:57 AM, Markos Chandras wrote:
On 02/19/15 06:10, Mike Gilbert wrote:
What saddens me the most is that these pointless threads are
becoming sort of a habit not because the reporter is really
offended by the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/19/2015 10:31 AM, Patrick Lauer wrote:
On Thursday 19 February 2015 10:07:30 Kristian Fiskerstrand wrote:
On 02/19/2015 09:57 AM, Markos Chandras wrote:
On 02/19/15 06:10, Mike Gilbert wrote: What saddens me the most
is that these
On Thu, 19 Feb 2015 19:34:28 +0800
Patrick Lauer patr...@gentoo.org wrote:
On Thursday 19 February 2015 12:31:27 Alexis Ballier wrote:
On Wed, 18 Feb 2015 22:48:27 +0100
Michał Górny mgo...@gentoo.org wrote:
Dnia 2015-02-18, o godz. 16:11:53
Mike Frysinger (vapier)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/19/15 13:38, Alexis Ballier wrote:
On Thu, 19 Feb 2015 19:34:28 +0800 Patrick Lauer
patr...@gentoo.org wrote:
On Thursday 19 February 2015 12:31:27 Alexis Ballier wrote:
On Wed, 18 Feb 2015 22:48:27 +0100
Michał Górny
On Thu, Feb 19, 2015 at 4:39 AM, Kristian Fiskerstrand k...@gentoo.org wrote:
On 02/19/2015 10:31 AM, Patrick Lauer wrote:
On Thursday 19 February 2015 10:07:30 Kristian Fiskerstrand wrote:
On 02/19/2015 09:57 AM, Markos Chandras wrote:
On 02/19/15 06:10, Mike Gilbert wrote: What saddens me
On Wed, 18 Feb 2015 15:13:31 -0500 Michael Orlitzky wrote:
The topic of a review workflow comes up frequently, but Gitlab, Gerrit,
etc. are blocked on a host of other problems that may never be resolved.
It would still be nice to be able to request reviews somewhere, and for
ebuilds, a mailing
Patrick Lauer:
On Thursday 19 February 2015 00:48:18 hasufell wrote:
Patrick Lauer:
Why is this package metadata missing the python herd for no reason?
Because the python herd doesn't currently maintain the package, nor did
they ask me to be co-maintainers.
So you put a python package in
Hello, everyone.
One month from today, on 2015-03-20 we are celebrating the 2.5yr
anniversary of EAPI=5 being officially approved. For this occasion,
Python team has prepared something special for you. This day we are
going to ban support for EAPI=4 in new ebuilds.
Today I have committed a QA
Rich Freeman:
Devs should be communicating with maintainers when they touch their
packages.
That's basically all I said.
The rest looks like imagination and flame about elephants and the end of
the world while I clearly didn't refer to any of that.
This isn't about protocol, it's about
pro: improved security in daemons (often network)
con: some packages might pull in libseccomp (~250KB)
there shouldn't be measurable runtime overhead here as the filtering is done by
a JIT in the kernel itself. if the kernel lacks support for seccomp, daemons
generally should fallback at
Extend the _pkg_str class with build_id, build_time, file_size, and
mtime attributes. These will be used to distinguish binary package
instances that have the same cpv. Package sorting accounts for
build_time, which will be used to prefer newer builds over older builds
when their versions are
On 02/19/15 06:38, Alexis Ballier wrote:
On Thu, 19 Feb 2015 19:34:28 +0800
Patrick Lauer patr...@gentoo.org wrote:
On Thursday 19 February 2015 12:31:27 Alexis Ballier wrote:
On Wed, 18 Feb 2015 22:48:27 +0100
Michał Górny mgo...@gentoo.org wrote:
Dnia 2015-02-18, o godz. 16:11:53
Mike
Michael Orlitzky m...@gentoo.org writes:
Would anyone else find gentoo-review@lists.g.o useful? I think a lot
of simple problems could be quickly caught with a second set of
eyeballs.
+1
Many opensource projects successfully run code review on mailing lists.
Why not try that. But this should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/19/15 21:14, Mike Frysinger wrote:
pro: improved security in daemons (often network) con: some
packages might pull in libseccomp (~250KB)
there shouldn't be measurable runtime overhead here as the
filtering is done by a JIT in the kernel
23 matches
Mail list logo
