[darcs-users] Google Summer of Code 2009 - ideas, students and mentors?

[Kari Hoijarvi]

Eric Kow wrote:
> * A Windows project: not sure what this would entail, but darcs on Windows
>   might need a bit of special attention
>       o 2008-08 : proposed as a priority for darcs 2.2 
> * A single-file database pristine cache, which should be faster and more robust
>   than our directory-based approach. e.g. a halfs filesystem.
>       o 2008: darcs 2.0.0 has hashed pristine, which is more robust, but it's not single-file. do we still want this? 
>   
For TortoiseDarcs, fast and complete querying of repository status would 
be very welcome.

Currently I run "darcs show files" and "darcs whatsnew -s 
[--look-for-adds]". It works, but has annoying lag. When you add a file, 
it still shows as not-in-darcs for a while. Continuous parsing of 
'_darcs/patches/pending' as TortoiseDarcs 1 did it is fragile, and not 
the way to go.

I'd like to have these two commands as a single report, with more 
information: timestamp, file size, type[dir/file], if the file is in 
conflict.

I'd like to get this also for a single file and for all the files in a 
single directory, not recursive.

Preferably this should be a library call, starting processes is expensive.

> * Keeping track of which patches affect which files, to speed up query
>   operations that affect only certain files (e.g. changes, diff, etc, when given
>   a filename argument).
>       o 2008-06 status: I don't think we do this yet. Still open? 
>   
Good and fast diff between two versions of a single file would be very 
welcome. It's the last feature I still miss from TortoiseCVS,

Kari