That 2 week time line has now reached the 9 week mark. The only update anyone has seen was 7 weeks ago, with a 'maybe today'. Isn't it time to get that code checked in so someone else can take over, and not have to start from scratch? Even if there isn't any actual working code, having any failed attempts in source control would still be instructive to whoever takes over delivering an actual fsck tool. On Tue, Sep 27, 2011 at 1:00 PM, Clemens Eisserer <linuxhippy@xxxxxxxxx> wrote: > +1 > > 2011/9/27 Jeff Putney <jeffrey.putney@xxxxxxxxx>: >> On Thu, Aug 18, 2011 at 3:50 PM, Chris Mason <chris.mason@xxxxxxxxxx> wrote: >>> I had hoped to get #1 out the door before I left on vacation and I still might >>> post it tonight. >>> >>> -chris >> >> I don't think this is the honest time line that people were looking >> for. Instead of playing more guessing games, how about we just get >> that source checked in so we can get more eyeballs on it. >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
