From: Thomas Lord <lord@emf.net>
To: git <git@vger.kernel.org>
Subject: arch 2.0 first source available (git related)
Date: Fri, 08 Jul 2005 17:12:27 -0700 [thread overview]
Message-ID: <1120867947.5882.2.camel@dev1.seyza.com> (raw)
The first source release and some very early documentation for Arch 2.0
("revc") is now ready!
Web page: <http://www.seyza.com/>
Source: <http://www.seyza.com/releases/revc-0.0x0.tar.gz>
Source (tar bundle) SHA1:
9c279f78e57a99d517ccf5b983960620ff6f2cf7
Source (tar bundle) size: 1732018
Some highlights: revc has only 10 core commands; there are about 165
functions; the source code is literally about 14K lines and is closer to
10K lines if you subtract out non-code boilerplate.
User complaints about tla 1.x being addressed in revc:
inventory is too complicated -- but is drastically simplified (almost
eliminated) in 2.0
we hate the funny filenames -- 2.0 requires only a single .revc
directory and you aren't expected to edit any files there. No more
{arch}, {arch}/=tagging-method, or deeply nested project-tree logs
the namespace blows -- 2.0 allows just about any revision name that
doesn't contain a slash character. There is a moderate limit on the
length of a revision name.
all this stuff about registering archives and making mirrors is hard to
learn -- and, in 2.0, it's all gone. You can use rsync to mirror stuff,
for starters. And all archives are anonymous -- there's no longer any
such thing as an archive name.
too much is too slow -- although the 2.0 code isn't especially optimized
yet, it seems to be hella snappy.
2.0 is very much git influenced but it brings some (imo significant)
improvements to the table.
-t
next reply other threads:[~2005-07-09 0:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-09 0:12 Thomas Lord [this message]
2005-07-09 11:39 ` arch 2.0 first source available (git related) Petr Baudis
2005-07-09 14:20 ` Thomas Lord
2005-07-11 19:39 ` Petr Baudis
2005-07-11 21:36 ` Thomas Lord
2005-07-11 23:31 ` Petr Baudis
2005-07-12 0:05 ` Thomas Lord
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1120867947.5882.2.camel@dev1.seyza.com \
--to=lord@emf.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.