summaryrefslogtreecommitdiff
path: root/hurd/translator/ext2fs.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2013-03-06 21:52:20 +0100
committerThomas Schwinge <tschwinge@gnu.org>2013-03-06 21:52:20 +0100
commit12c341b917921eb631026ec44a284c4d884e5de6 (patch)
treec7dc37f605152f5fb6e2d67d6460f78496e3de3d /hurd/translator/ext2fs.mdwn
parent53e5e4c139e1b239760434d10e74addd0e89593d (diff)
IRC.
Diffstat (limited to 'hurd/translator/ext2fs.mdwn')
-rw-r--r--hurd/translator/ext2fs.mdwn38
1 files changed, 37 insertions, 1 deletions
diff --git a/hurd/translator/ext2fs.mdwn b/hurd/translator/ext2fs.mdwn
index 13a1d9ec..65361ff4 100644
--- a/hurd/translator/ext2fs.mdwn
+++ b/hurd/translator/ext2fs.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2007, 2008, 2010, 2011, 2012 Free Software
+[[!meta copyright="Copyright © 2007, 2008, 2010, 2011, 2012, 2013 Free Software
Foundation, Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
@@ -89,6 +89,42 @@ small backend stores, like floppy devices.
<youpi> which can be quite probable
+#### [[libpager]] API change
+
+##### IRC, freenode, #hurd, 2013-03-04
+
+ <braunr> youpi: i don't remember exactly your answer when i asked about
+ considering the ext2 large store patch for merging
+ <youpi> there's just an API change that it introduces
+ <youpi> but otherwise I'd say we should just do it
+ <braunr> ok
+ <youpi> I've just checked the API change again
+ <youpi> it's simply adding a notify_on_evict parameter
+ <youpi> and a pager_notify_evict callback
+ <braunr> yes
+ <youpi> I'd say we mostly need to polish this
+ <youpi> ah, there is the same parameter on diskfs_start_disk_pager
+
+
+#### `EXT2FS_DEBUG`
+
+##### IRC, freenode, #hurd, 2013-03-04
+
+ <braunr> youpi: do we want EXT2FS_DEBUG defined upstream ?
+ <youpi> I don't really have an opinion on this
+ <youpi> stuffing it in the large store patch is not good of course
+ <youpi> I wonder whether we want it by default.
+ <braunr> it is currently defined by the patch
+ <braunr> (in the debian package i mean)
+ <youpi> I've just seen that yes
+ <braunr> i won't include it upstream, and if we decide to keep this
+ behaviour, we can add a patch just for that
+ <braunr> or a define
+ <braunr> err
+ <braunr> a configure option
+ <youpi> ok
+
+
## Sync Interval
[[!tag open_issue_hurd]]