On 2014 Jul 29 (Tue) at 00:19:43 +0200 (+0200), Alexander Bluhm wrote:
:On Sun, Jul 13, 2014 at 04:05:41PM +0200, Mark Kettenis wrote:
:> Some people have reported that apmd -A makes their machines hang.
:> Could those people try the diff below and see whether it helps?
:
:I am running this diff an
On Sun, Jul 13, 2014 at 04:05:41PM +0200, Mark Kettenis wrote:
> Some people have reported that apmd -A makes their machines hang.
> Could those people try the diff below and see whether it helps?
I am running this diff and apmd -A on a thinkpad T430s. The machine
is idle, the X11 blank screen sa
Hello Miod,
Will certainly do, thanks for your input!
Miod Vallat wrote:
> > I recently used cppcheck on mg and I got this message:
> >
> > [macro.c:41]: (error) Memory pointed to by 'lp1' is freed twice.
> >
> > Looking at the code:
> >
> > /* free lines allocated for string arguments */
> >
Hi Stefan,
Stefan Sperling wrote on Tue, Jul 15, 2014 at 12:17:08PM +0200:
> cvs log -r1.x shows the log entry for HEAD, instead of the log entry
> for 1.x as cvs -r 1.x does.
The typos in this sentence confused me so thoroughly that when first
looking at your mail, i didn't get your intent at a
Theo de Raadt wrote on Mon, Jul 28, 2014 at 09:20:36AM -0600:
> The mention of sendsyslog is not acceptable. When this man page shows up
> on some other system, it will be an Xr pointing to nowhere.
>
> The information is too specific. Frankly, noone will care. Old systems
> will continue doin
>> Unfortunately, no.
>>
>> The ssh manual pages are also used by the -portable effort. We do not
>> bother documenting these divergences; there is little harm.
>>
>> Actually you could submit a new diff which suggest that logging
>> "might" need a /dev/log setup. If written carefully to cover
Theo de Raadt wrote on Fri, Jul 18, 2014 at 03:04:28PM -0600:
> Unfortunately, no.
>
> The ssh manual pages are also used by the -portable effort. We do not
> bother documenting these divergences; there is little harm.
>
> Actually you could submit a new diff which suggest that logging
> "might
On Sun, Jul 27, 2014 at 9:14 AM, frantisek holop wrote:
> is there a reason why this check should be done twice?
>
If the code is inextricable, check the history of how it got that way. In
this case, there was a mostly mechanical elimination of unnecessary
__BSD_VISIBLE clauses which changed di
I'm looking for a few people to test some additional
radeondrm fixes from the recently released Linux 3.8.13.27:
https://lkml.org/lkml/2014/7/25/621
In particular on newer asics with displayport/eDP as I
can only test on r100/lvds at the moment.
commit 85cdd5e933c0f9fe3262067e707eed565db46378
Aut
