From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] github.com/9fans + plan9port on git
Date: Mon, 17 Nov 2014 18:18:56 -0800 [thread overview]
Message-ID: <20141118021856.83745B82A@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Mon, 17 Nov 2014 01:14:22 CST." <F1662E85-7D66-4D52-9A75-BD5F196CD79B@corpus-callosum.com>
On Mon, 17 Nov 2014 01:14:22 CST Jeff Sickel <jas@corpus-callosum.com> wrote:
>
> I look forward to Go's fifth version control system. Hopefully that
> one will be concise, written in Go, and not gimmicky with cartoon
> advertising everywhere.
I don't know about Go (the Go guys are probably already
suffering from a massive VCS fatigue), but if you want to play
with this idea, there is venti! Vac can take a previous score
to do incremental archiving. If you add sepcial blocks that
store two parent scores + some metadata, it can represent a
merge point. Mapping to a filesystem view would require some
thought but I think most of the key pieces are already in
place. I have a whole bunch of paper projects based on venti!
next prev parent reply other threads:[~2014-11-18 2:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 3:49 Russ Cox
2014-11-17 4:01 ` [9fans] " lucio
2014-11-17 7:14 ` Jeff Sickel
2014-11-17 13:38 ` erik quanstrom
2014-11-17 22:53 ` Kurt H Maier
2014-11-18 8:26 ` Skip Tavakkolian
2014-11-18 2:18 ` Bakul Shah [this message]
2014-11-18 2:28 ` erik quanstrom
2014-11-18 3:08 ` Bakul Shah
2014-11-18 3:15 ` erik quanstrom
2014-11-18 3:16 ` minux
2014-11-18 8:39 ` Skip Tavakkolian
2014-11-18 8:57 ` Ramakrishnan Muthukrishnan
2014-11-18 13:24 ` Joseph Stewart
2014-11-18 13:41 ` Joseph Stewart
2014-11-17 9:08 ` Carsten Kunze
2014-11-17 9:26 ` Carsten Kunze
2014-11-17 9:42 ` David du Colombier
2014-11-17 12:49 ` lucio
2014-11-17 12:57 ` David du Colombier
2014-11-17 19:03 ` Ryan Gonzalez
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=20141118021856.83745B82A@mail.bitblocks.com \
--to=bakul@bitblocks.com \
--cc=9fans@9fans.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).