On Wed, Jul 04, 2012 at 08:29:13AM +0200, Thomas Schwinge wrote:
> On Tue, 3 Jul 2012 21:19:12 +0200, Richard Braun wrote:
> > Unless it's very easy to use submodules, we should use one repository.
> > Other projects with much more content and history have showed it's
> > perfectly sane to keep th
Hi!
On Sat, 30 Jun 2012 18:22:50 +0200, Guillem Jover wrote:
> On Fri, 2012-06-22 at 10:47:20 +0200, Guillem Jover wrote:
> > Could we get MiG 1.3.2 released at least? There's some pending changes in
> > the Debian packaging I'd like to upload before the freeze (on 2012-06-30),
> > but I'd rather
Hi!
On Tue, 3 Jul 2012 21:19:12 +0200, Richard Braun wrote:
> On Sun, Jul 01, 2012 at 12:59:47PM +0700, Ivan Shmakov wrote:
> > > Samuel Thibault writes:
> >
> > > Should we keep procfs in a separate repository, or merge it into the
> > > main hurd repository?
> >
> > > Generally enough
On Tue, Jul 03, 2012 at 09:13:36PM -0300, Samuel Thibault wrote:
> Richard Braun, le Tue 03 Jul 2012 23:13:26 +0200, a écrit :
> > * ext2fs/inode.c (diskfs_node_iterate): allocate the temporary node
> > table from the heap instead of the stack.
>
> That can be quite a lot for the stack indeed, tha
Richard Braun, le Tue 03 Jul 2012 23:13:26 +0200, a écrit :
> * ext2fs/inode.c (diskfs_node_iterate): allocate the temporary node
> table from the heap instead of the stack.
That can be quite a lot for the stack indeed, thanks!
Samuel
* ext2fs/inode.c (diskfs_node_iterate): allocate the temporary node
table from the heap instead of the stack.
Signed-off-by: Richard Braun
---
ext2fs/inode.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/ext2fs/inode.c b/ext2fs/inode.c
index f25cc1f..2da8a95
On Sun, Jul 01, 2012 at 12:59:47PM +0700, Ivan Shmakov wrote:
> > Samuel Thibault writes:
>
> > Should we keep procfs in a separate repository, or merge it into the
> > main hurd repository?
>
> > Generally enough, did we write a guideline somewhere as to what
> > should be in the main h
Hello,
I'm currently working on the VM cache as implemented by GNU Mach, and
more specifically on the maximum cached objects limit, the goal being
to remove it and let memory pressure be the only flush trigger.
But when removing the limit, I experience far more ext2fs stability
issues than usual.
