gnu-arch-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Re: Recover a deleted file


From: Tom Lord
Subject: Re: [Gnu-arch-users] Re: Recover a deleted file
Date: Sun, 13 Jun 2004 18:45:46 -0700 (PDT)

    > From: Juliusz Chroboczek <address@hidden>
    > >> That's because tla is about making complex things possible.  Making
    > >> simple things simple has been forgotten somewhere along the way.

    > MB> That's a pretty bizarre thing to say.  There are many common 
operations
    > MB> which are insanely easier with tla than with CVS;

    > The (correctly designed) data structures used by tla make a lot of
    > things that are difficult or impossible to do with CVS reasonably easy
    > to do with tla; however, there are a lot of things that everyone needs
    > and that should be completely trivial to do with tla but aren't.

    > We are all annoyed by these lacks when we first use tla, and then we
    > all end up with collections of silly scripts.

    > Examples include:
    > 
    >   - revert;
    >   - switch;
    >   - register-archive + archive-mirror + get;
    >   - archive-mirror + update or just update, depending on the archive;
    >   - diff patch-A patch-B and diff branch-A branch-B;
    >   - export and release;
    >   - branch.

    > I think the problem with tla is that it insists on exposing too much
    > of the implementation, and hence ends up being mighty unfriendly.  A
    > good example is the third in the list above (register + mirror + get):
    > from an implementer's point of view, these are three distinct
    > activities; from a user's point of view, it's a single task (get the
    > latest devel tree of tla in such a way that I can conveniently update
    > later).

I think you are exactly on mark.  Many of the recent "FEATURE PLAN"
posts address such issues.   The real question is how best to
implement those and other planned features and that's what I'm working
on right now.

-t





reply via email to

[Prev in Thread] Current Thread [Next in Thread]