Date: Sat, 11 Sep 2010 19:16:16 -0400 From: Aryeh Friedman <aryeh.friedman@gmail.com> To: perryh@pluto.rain.com, freebsd-hackers@freebsd.org Subject: Re: How to disallow logout Message-ID: <AANLkTi=dihwkM30eLi4=JPnKeGtEM1VTtxc=Rez0QvnO@mail.gmail.com> In-Reply-To: <4c8c0cb4.n0Z%2Br%2BTIC4vzdXnS%perryh@pluto.rain.com> References: <AANLkTin93An%2BUORiwHe%2BXdcgxj%2BpeXV1B2xvu81r_1CG@mail.gmail.com> <201009111510.o8BFAnJ9011318@lurza.secnetix.de> <AANLkTimzokJ_yp3uOe93FUpAs7AOznhKBBDdHxiQ1n9_@mail.gmail.com> <4c8c0cb4.n0Z%2Br%2BTIC4vzdXnS%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Since we have been using aegis for years and know it like the back of our hand I don't want to learn a new tool... but I think your right I am going to forward/cross post this entire thread to the aegis mailing list. On Sat, Sep 11, 2010 at 7:11 PM, <perryh@pluto.rain.com> wrote: > Aryeh Friedman <aryeh.friedman@gmail.com> wrote: > >> I would prefer to have the plain text around after a power failure >> because it could be several days of work ... > > Ideally there should be _some_ mechanism for committing unfinished > work to a (probably encrypted) repository on, at least, a daily > basis. > > The more I see of this thread, the more it seems that the problem > is largely the fault of the particular VCS being used. =A0A VCS that > demands a "review" step before anything can be checked in, even on a > "work in progress" branch as opposed to the mainline, seems a poor > fit for a project in which developers are not permitted to see one > anothers code. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=dihwkM30eLi4=JPnKeGtEM1VTtxc=Rez0QvnO>