From: "Shawn O. Pearce" <spearce@spearce.org>
To: K??rlis Repsons <karlis.repsons@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Which VCS besides git?
Date: Tue, 2 Mar 2010 07:41:28 -0800 [thread overview]
Message-ID: <20100302154128.GE28997@spearce.org> (raw)
In-Reply-To: <201003021538.15276.karlis.repsons@gmail.com>
K??rlis Repsons <karlis.repsons@gmail.com> wrote:
> On Tuesday 02 March 2010 15:28:21 Shawn O. Pearce wrote:
> > K??rlis Repsons <karlis.repsons@gmail.com> wrote:
> > > 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?
> >
> > Most of the distributed VCS systems do this. I know Mercurial is
> > functionally identical to Git in this regard. Maybe even Monotone
> > and Bazaar are as well, but I'm less familiar with those.
>
> And svn doesn't?
I don't know about SVN. I only used it for a few months between
CVS and BitKeeper. After that, I jumped pretty fast into Git and
didn't care about how Subversion works internally.
You might want to ask on the SVN mailing list rather than the Git
mailing list about SVN specific details...
--
Shawn.
next prev parent reply other threads:[~2010-03-02 15: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 [this message]
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
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=20100302154128.GE28997@spearce.org \
--to=spearce@spearce.org \
--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).