* distinguished branch First of all, as you all know, in CVS there is a distinguished branch name, "HEAD", which is the default branch. It is usually used to hold most forward development. I'd like t
Looks like updating neon, or rigging tla to use an external libneon, is becoming more important. -- Forwarded message from Wichert Akkerman <address@hidden> -- Hi Andrew, can you please look into thi
What are you going to do about all those revisions that already use the existing paths? For example, simply untarring certain base-0 revisions will want to create paths of the current sort. If you c
Hi Doran! How useful, really, is automatic registration of archive names beyond about two dozen anyway? I have 20-odd archives registered and already that's too much to reliably remember without some
[snip] How useful, really, is automatic registration of archive names beyond about two dozen anyway? I have 20-odd archives registered and already that's too much to reliably remember without some ki
The original agenda for 1.1, aside from simple bug fixes, was: *) the inode signature optimization *) =tagging-method generalization *) fancier support for "partial commits" The agenda changed in a
The parts I can safely answer from memory: Privately (i.e, before announcements or distribution): November 2001. (An earlier system was scrapped -- approximately early 2000, if I recall correctly.)
You can safely stick files named '=README' in an archive and they will (because of the namespace syntax) not be confused for categories, branches, or versions by tla. They also won't be (and shouldn
With things like ViewARCH, Alexander's archive list and `tla grab` happening all over the place, I'm feeling the need for some human-readable meta-info attached to archives. The address@hidden syntax
As some of you may know, and others may not care. I'm working on a GUI shell for arch. I wanted to start the search for an icon now. I think that the ViewARCH project could probably make use of the s
Ah... The location of "address@hidden" also moved. New location: address@hidden http://arch.bluegate.org:8080/{archives}/address@hidden address@hidden/ViewARCH--tez--0.0.1 - Tez
I use it to note the flavour of my commit, i.e. 'merge', 'bugfix', ... If I want to have a look at only the merges, I can search by keyword; using grep, or a tool like Perspective or ViewARCH. Note t
Possibly true, but what if tla-contrib--devo--1.1 contained a configs/ dir itself, with a config for each part? configs/ cvs2arch.contrib bash-completion.contrib ... viewarch.contrib perspective.cont
I quite like this idea. Given a revision library and ViewArch on the server, you also get diffs between revisions like on the wiki. However, to protect ourselves from potential vandalism, I think it