Guillaume Hoffmann wrote: > Hi Ben (and others), > > sorry for being missing-in-action for so long, The combined effect of > end-of-year celebrations and summer holidays (here in the south > hemisphere) removed me from darcs development for a long time. Next > week I'll be able to come back to working on it. > > I think we can aim at finishing darcs 2.10 by end of February.
That sounds pretty optimistic to me... > In > november and december Ganesh and I worked on patch index memory use, > which finally became acceptable. > > Fortunately we don't have a big divergence between screened, reviewed > and branch-2.10. > > I saw there was work on encoding, and on the flag system, which are > topics for which I'm not an expert. Can you see if you can > (self-)accept patches related to these topics? I'll try to do that for those patches I can understand ;-) Could you give me advice how to make accepting (and screening, too, for that matter) a bit more automatic? Currently I push them (e.g. to darcs- unsta...@darcs.net:screened), then go to the tracker and change the status, which is a bit error prone IMO. > Here is the list of open bugs for 2.10: http://tinyurl.com/nay7jq4 I added the latest problem I detected with darcs convert export to the 2.10 milestone, as this could cause serious trouble... Cheers Ben -- "Make it so they have to reboot after every typo." -- Scott Adams _______________________________________________ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
