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: Tue, 02 Mar 2010 08:12:22 -0800 (PST) [thread overview]
Message-ID: <m3y6ialn3z.fsf@localhost.localdomain> (raw)
In-Reply-To: <201003021455.52483.karlis.repsons@gmail.com>
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?
If you want to know which VCS beside Git use cryptographic hash
function over commit info and commit parentage as commit id, then both
Monotone (from which Git borrowed this idea) and Mercurial use it.
Bazaar, if I understand it correctly, and from what I remember, uses
some UUID which includes commit digest as a commit identifier, but I
don't know if Bazaar have immutable history.
In Subversion you can change svn:log (or something like that)
property, i.e. change commit message, after the fact; I don't think
there is any check for that. CVS doesn't support changesets, so it is
out of question.
I don't know about Darcs, or BitKeeper, or ClearCase, or Perforce.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-03-02 16:12 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 [this message]
2010-03-02 16:22 ` Kārlis Repsons
2010-03-02 16:38 ` Ben Walton
2010-03-03 1:41 ` Jakub Narebski
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=m3y6ialn3z.fsf@localhost.localdomain \
--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).