reorg
This commit is contained in:
parent
fed1d3c1f5
commit
81f71e57b9
15 changed files with 22 additions and 0 deletions
|
@ -18,6 +18,7 @@ To get a feel for it, see the [[walkthrough]].
|
|||
* [[install]]
|
||||
* [[news]]
|
||||
* [[bugs]]
|
||||
* [[todo]]
|
||||
* [[contact]]
|
||||
"""]]
|
||||
|
||||
|
|
4
doc/todo.mdwn
Normal file
4
doc/todo.mdwn
Normal file
|
@ -0,0 +1,4 @@
|
|||
This is git-annex's todo list. Link items to [[todo/done]] when done.
|
||||
|
||||
[[!inline pages="./todo/* and !./todo/done and !link(done)
|
||||
and !*/Discussion" actions=yes postform=yes show=0 archive=yes]]
|
4
doc/todo/done.mdwn
Normal file
4
doc/todo/done.mdwn
Normal file
|
@ -0,0 +1,4 @@
|
|||
recently fixed [[todo]] items.
|
||||
|
||||
[[!inline pages="./* and link(./done) and !*/Discussion" sort=mtime show=10
|
||||
archive=yes]]
|
13
doc/todo/parallel_possibilities.mdwn
Normal file
13
doc/todo/parallel_possibilities.mdwn
Normal file
|
@ -0,0 +1,13 @@
|
|||
One of my reasons for using haskell was that it provides the possibility of
|
||||
some parallell processing. Although since git-annex hits the filesystem
|
||||
heavily and mostly runs other git commands, maybe not a whole lot.
|
||||
|
||||
Anyway, each git-annex command is broken down into a series of independant
|
||||
actions, which has some potential for parallelism.
|
||||
|
||||
Probably they would need to be split further. Each action currently has 3
|
||||
distinct phases, basically "check", "do", and "record". If the check action
|
||||
returned a do action that returned a record action, then it could easily
|
||||
make sense to parallelize the check actions and start on the do actions
|
||||
(which probably won't parallelize well) while they are still being
|
||||
generated, and possibly parallelize the record actions at the end.
|
Loading…
Reference in a new issue