On Fri, 2012-12-07 at 09:48 +0100, Rik Theys wrote:
> Hi,
>
> On 12/06/2012 02:51 PM, Ben Hutchings wrote:
> > On Thu, 2012-12-06 at 13:58 +0100, Rik Theys wrote:
> >> On 12/06/2012 01:29 PM, Ben Hutchings wrote:
> > It is not too difficult to fix up the conflicts. But this is a fairly
>
Hi,
On 12/07/2012 09:48 AM, Rik Theys wrote:
Hi,
On 12/06/2012 02:51 PM, Ben Hutchings wrote:
On Thu, 2012-12-06 at 13:58 +0100, Rik Theys wrote:
On 12/06/2012 01:29 PM, Ben Hutchings wrote:
It is not too difficult to fix up the conflicts. But this is a
fairly
big change, so I think this bu
Hi,
On 12/06/2012 02:51 PM, Ben Hutchings wrote:
On Thu, 2012-12-06 at 13:58 +0100, Rik Theys wrote:
On 12/06/2012 01:29 PM, Ben Hutchings wrote:
It is not too difficult to fix up the conflicts. But this is a fairly
big change, so I think this bug should now be 'wontfix' for wheezy.
Sorry we
On Thu, 2012-12-06 at 13:58 +0100, Rik Theys wrote:
> On 12/06/2012 01:29 PM, Ben Hutchings wrote:
> >>> It is not too difficult to fix up the conflicts. But this is a fairly
> >>> big change, so I think this bug should now be 'wontfix' for wheezy.
> >>> Sorry we didn't get it fixed earlier.
> >>
On 12/06/2012 01:29 PM, Ben Hutchings wrote:
It is not too difficult to fix up the conflicts. But this is a fairly
big change, so I think this bug should now be 'wontfix' for wheezy.
Sorry we didn't get it fixed earlier.
Sorry to hear that. Would a patch that simply increases the static
number
On Thu, 2012-12-06 at 10:58 +0100, Rik Theys wrote:
> Hi,
>
> On 12/01/2012 11:10 PM, Ben Hutchings wrote:
> > On Fri, 2012-11-30 at 11:10 +0100, Rik Theys wrote:
> > [...]
> >> I cherry picked commits 5ef30ee53b187786e64bdc1f8109e39d17f2ce58 and
> >> 5195d8e217a78697152d64fc09a16e063a022465 and t
Hi,
On 12/01/2012 11:10 PM, Ben Hutchings wrote:
On Fri, 2012-11-30 at 11:10 +0100, Rik Theys wrote:
[...]
I cherry picked commits 5ef30ee53b187786e64bdc1f8109e39d17f2ce58 and
5195d8e217a78697152d64fc09a16e063a022465 and tried to compile the
result, but it failed with the following error:
kern
On Fri, 2012-11-30 at 11:10 +0100, Rik Theys wrote:
[...]
> I cherry picked commits 5ef30ee53b187786e64bdc1f8109e39d17f2ce58 and
> 5195d8e217a78697152d64fc09a16e063a022465 and tried to compile the
> result, but it failed with the following error:
>
> kernel/auditsc.c:2189: error: conflicting typ
Hi,
On 11/30/2012 08:18 AM, Rik Theys wrote:
On 11/29/2012 01:10 PM, Rik Theys wrote:
On 11/25/2012 01:12 AM, Jonathan Nieder wrote:
On some of our servers, we periodically see "name_count maxed,
losing inode data" messages in the kernel log.
As you mentioned, this is said to be fixed by
On 11/29/2012 01:10 PM, Rik Theys wrote:
On 11/25/2012 01:12 AM, Jonathan Nieder wrote:
On some of our servers, we periodically see "name_count maxed,
losing inode data" messages in the kernel log.
As you mentioned, this is said to be fixed by
commit 5195d8e217a7
Author: Eric Paris
On 11/25/2012 01:12 AM, Jonathan Nieder wrote:
On some of our servers, we periodically see "name_count maxed,
losing inode data" messages in the kernel log.
As you mentioned, this is said to be fixed by
commit 5195d8e217a7
Author: Eric Paris
Date: Tue Jan 3 14:23:05
reassign 631799 src:linux linux-2.6/2.6.32-35
tags 631799 + upstream patch moreinfo
quit
Hi Rik,
Rik Theys wrote:
> On some of our servers, we periodically see "name_count maxed,
> losing inode data" messages in the kernel log.
As you mentioned, this is said to be fixed by
commit 5195d
12 matches
Mail list logo
