Are you removing any inappropriate/hostile words in the tree (if exists)?
On Sun, Apr 26, 2015 at 10:39:00PM +0900, Izumi Tsutsui wrote:
Please don't assume all tier II users check auto-build reports
even every month.
I would expect portmaster at least to check much more often than once a
month or at least request notification.
Joerg
Izumi Tsutsui tsut...@ceres.dti.ne.jp writes:
joerg@ wrote:
Please don't commit untested and broken fix.
Please file a PR instead if you can't test it.
I agree with Christos that leaving the build broken is worse. The
alternative band aids are much more involved, too. That shouldn't
On Sun, Apr 26, 2015 at 10:07:32AM -0400, Greg Troxel wrote:
Izumi Tsutsui tsut...@ceres.dti.ne.jp writes:
joerg@ wrote:
Please don't commit untested and broken fix.
Please file a PR instead if you can't test it.
I agree with Christos that leaving the build broken is worse.
On Apr 26, 10:39pm, tsut...@ceres.dti.ne.jp (Izumi Tsutsui) wrote:
-- Subject: Re: CVS commit: src/distrib/atari/floppies/install
| christos@ wrote:
|
| | Please don't commit untested and broken fix.
| | Please file a PR instead if you can't test it.
|
| I can't test, and it is broken
joerg@ wrote:
Please don't commit untested and broken fix.
Please file a PR instead if you can't test it.
I agree with Christos that leaving the build broken is worse. The
alternative band aids are much more involved, too. That shouldn't stop
the second point from that list.
If you
On Sun, Apr 26, 2015 at 10:54:41PM +0900, Izumi Tsutsui wrote:
joerg@ wrote:
Please don't commit untested and broken fix.
Please file a PR instead if you can't test it.
I agree with Christos that leaving the build broken is worse. The
alternative band aids are much more involved,
Joerg Sonnenberger jo...@britannica.bec.de writes:
On Sun, Apr 26, 2015 at 10:07:32AM -0400, Greg Troxel wrote:
A broken build is evidence that the prior commits were not tested,
and thus need fixing. Objecting to fixing the build without testing
should be a far lower priority than
(note I don't even know how long atari build has been broken)
This problem often rises when build failure is caused by MI changes
without particular annoucements.
If someone[tm] can update our autobuild script, it would be great..
- less frequent (weekly or semi-monthly?) builds for tierII ports
joerg@ wrote:
Please don't commit untested and broken fix.
Please file a PR instead if you can't test it.
I agree with Christos that leaving the build broken is worse. The
alternative band aids are much more involved, too. That shouldn't stop
the second point from that list.
christos@ wrote:
| Please don't commit untested and broken fix.
| Please file a PR instead if you can't test it.
I can't test, and it is broken already. For months...
Having the build broken is bad, because it means that any changes
after the break are not even compile-tested.
Please file
Am 25.04.15 um 11:24 schrieb David Holland:
On Fri, Apr 24, 2015 at 12:20:17AM +, Blue Rats wrote:
Module Name: src
Committed By: rodent
Date: Fri Apr 24 00:20:17 UTC 2015
Modified Files:
src/share/misc: acronyms
Log Message:
+BB = baby
On Sun, Apr 26, 2015 at 06:09:37PM +0900, Masao Uebayashi wrote:
Are you removing any inappropriate/hostile words in the tree (if exists)?
If there's stuff of the same sort as the acronyms that got pruned,
perhaps so. Don't know of any, but that doesn't mean it's not there.
(routine bad
Am 25.04.15 um 18:07 schrieb Alan Barrett:
On Sat, 25 Apr 2015, rod...@netbsd.org wrote:
I'm responding to the recent posts ITT, because it seems there's some
misunderstanding:
I had no idea what ITT meant, until I looked it up. (ITT = in this
thread, apparently).
1) What has been
14 matches
Mail list logo
