From: Jakub Narebski <jnareb@gmail.com>
To: "Kārlis Repsons" <karlis.repsons@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Which VCS besides git?
Date: Wed, 3 Mar 2010 02:41:16 +0100 [thread overview]
Message-ID: <201003030241.16959.jnareb@gmail.com> (raw)
In-Reply-To: <201003021622.22196.karlis.repsons@gmail.com>
Kārlis Repsons wrote:
> On Tuesday 02 March 2010 16:12:22 Jakub Narebski wrote:
> > Kārlis Repsons <karlis.repsons@gmail.com> writes:
> > > which VCS besides git provide chaining of commits with help of some
> > > cryptographic hash function, warning about or not allowing commits to be
> > > deleted on an equivalent of pull action, so that all added pieces of data
> > > can be retained securely on client side?
> >
> > Could you rephrase your request in more clear way?
>
> On top of what you wrote already, I'd like to know which VCS have immutable
> history, which can all be stored (say, gradually accumulated) on clientside? I
> hope, that explained the idea...
As I wrote, all VCS which use cryptographic hash function (digest) for
commit identifier have immutable history.
All distributed VCS (DVCS) store whole[*] history with checkout. There
isn't (beside _social_ reasons) any distinction between different repos:
there is no client - server model (so no "clientside"), but rather peer
2 peer model. See http://en.wikipedia.org/wiki/List_of_revision_control_software#Distributed_model
(from OSS ones I'd say Git, Mercurial, Bazaar, Darcs, Monotone count).
[*] well, with possibly some exceptions, like shallow clone, or selecting
branches to clone.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2010-03-03 1:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 14:55 Which VCS besides git? Kārlis Repsons
2010-03-02 15:28 ` Shawn O. Pearce
2010-03-02 15:38 ` Kārlis Repsons
2010-03-02 15:41 ` Shawn O. Pearce
2010-03-02 16:12 ` Jakub Narebski
2010-03-02 16:22 ` Kārlis Repsons
2010-03-02 16:38 ` Ben Walton
2010-03-03 1:41 ` Jakub Narebski [this message]
2010-03-03 11:58 ` Felipe Contreras
2010-03-03 12:12 ` Bruce Stephens
2010-03-03 12:31 ` Felipe Contreras
2010-03-03 12:48 ` Ben Walton
2010-03-03 12:49 ` Miklos Vajna
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=201003030241.16959.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=karlis.repsons@gmail.com \
/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).