From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <5d375e920901290412k3e48d87dy5261c9b1f1681127@mail.gmail.com>
References: <5d375e920901272106v77866afeua36bb6dc8b7feeca@mail.gmail.com>
	<f3d7cb9073cb012bf3631b3114d57382@quanstro.net>
	<5d375e920901290412k3e48d87dy5261c9b1f1681127@mail.gmail.com>
Date: Thu, 29 Jan 2009 08:15:05 -0800
Message-ID: <13426df10901290815u470ef46sba37c7f6652062e4@mail.gmail.com>
From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Sources Gone?
Topicbox-Message-UUID: 8e18ebcc-ead4-11e9-9d60-3106f5b1d025

On Thu, Jan 29, 2009 at 4:12 AM, Uriel <uriel99@gmail.com> wrote:

> All this has been solved by git and hg; and git and hg would *never*
> wipe out your local files simply because the backing store for the
> repository you are pulling from happens to break,

Have you used git much? Sure, it's nice. Have you tried it when it
hits 6 gbyte size as we have here, and repo is filled with binaries,
not just source?

It gets rather slow. At least for us. Also, as has been pointed out,
it is not unsurprisingly optimized to Linux. MacOS users complain to
me that it doesn't do well on MacOS.

Finally, the tools!

git                      git-get-tar-commit-id    git-read-tree
git-add                  git-grep                 git-rebase
git-add--interactive     git-gui                  git-rebase--interactive
git-am                   git-hash-object          git-receive-pack
git-annotate             git-http-fetch           git-reflog
git-apply                git-http-push            git-relink
git-archimport           git-imap-send            git-remote
git-archive              git-index-pack           git-repack
git-bisect               git-init                 git-repo-config
git-blame                git-init-db              git-request-pull
git-branch               git-instaweb             git-rerere
git-bundle               gitk                     git-reset
git-cat-file             git-log                  git-revert
git-check-attr           git-lost-found           git-rev-list
git-checkout             git-ls-files             git-rev-parse
git-checkout-index       git-ls-remote            git-rev-tree
git-check-ref-format     git-ls-tree              git-rm
git-cherry               git-mailinfo             git-send-email
git-cherry-pick          git-mailsplit            git-send-pack
git-citool               git-merge                git-shell
git-clean                git-merge-base           git-shortlog
git-clone                git-merge-file           git-show
git-commit               git-merge-index          git-show-branch

And it all seemed so simple in the early days.

Why not just understand and fix replica, instead of throwing stones?
What's the point? To replace actual coding with verbiage?

The part that confuses me most is that, IIRC, you were extolling the
virtues of venti a few days ago (with which I agree), particularly
that it is "rock solid" (true). But the current problem was a venti
outage. Conclusion: stuff happens. When stuff happens, bugs are
exposed. Bugs can be fixed. Erik's already proposed one fix, let's get
more.

ron