On Fri, 27 Jan 2017 13:20:10 +
"M. J. Everitt" wrote:
> I don't think anyone truly wants a /_desert_/ Rich, but perhaps you
> meant a /*dessert*/ ?!
You never know, he could be a giant sand worm, digging through the deserts
of spice on Dune.
pgpyt9mdKwDff.pgp
On 01/27/2017 07:41 AM, Rich Freeman wrote:
On Fri, Jan 27, 2017 at 7:06 AM, Dirkjan Ochtman wrote:
On Fri, Jan 27, 2017 at 8:26 AM, Michał Górny wrote:
I should point out that:
1) CI is detecting this kind of issues much faster than you are,
and
On 27/01/17 12:41, Rich Freeman wrote:
>
> I'm a little concerned that stuff like this starts to end up working
> like collective punishment. Fred over here broke the tree, so nobody
> gets to have desert or recess today; you all know what to do with Fred
> when he's looking to sit next to
On Fri, Jan 27, 2017 at 7:06 AM, Dirkjan Ochtman wrote:
>
> On Fri, Jan 27, 2017 at 8:26 AM, Michał Górny wrote:
>> I should point out that:
>>
>> 1) CI is detecting this kind of issues much faster than you are,
>> and reporting them both to the committer and
Wow, Michał, this email comes off as pretty harsh to me... Is that
really necessary?
On Fri, Jan 27, 2017 at 8:26 AM, Michał Górny wrote:
> I should point out that:
>
> 1) CI is detecting this kind of issues much faster than you are,
> and reporting them both to the committer
On Thu, 26 Jan 2017 18:48:39 -0500
Doug Freed wrote:
> This particular issue has already been fixed, but I'll be forwarding
> all these emails to the list from now on (I have to do that manually,
> because there are some that aren't anybody's fault, and I don't need
> to spam
On 26/01/17 06:48 PM, Doug Freed wrote:
> This is the email I get when a Manifest is missing DIST entries; it's
> more verbose than it needs to be, but I'd rather have more than less.
> In this particular case, the developer that made the bad commit likely
> had something they were working on in
On 27/01/17 00:55, NP-Hardass wrote:
> On 01/26/2017 06:48 PM, Doug Freed wrote:
>> This is the email I get when a Manifest is missing DIST entries; it's
>> more verbose than it needs to be, but I'd rather have more than less.
>> In this particular case, the developer that made the bad commit
On 01/26/2017 06:48 PM, Doug Freed wrote:
> This is the email I get when a Manifest is missing DIST entries; it's
> more verbose than it needs to be, but I'd rather have more than less.
> In this particular case, the developer that made the bad commit likely
> had something they were working on in
This is the email I get when a Manifest is missing DIST entries; it's
more verbose than it needs to be, but I'd rather have more than less.
In this particular case, the developer that made the bad commit likely
had something they were working on in sys-cluster/torque added to the
git index (ie,
10 matches
Mail list logo