From: Kevin Ballard <kevin@sb.org>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: MDellerus <mdellerus@yahoo.com>, git@vger.kernel.org
Subject: Re: can subversion 1.6 be made "just as distributed as git"?
Date: Thu, 4 Nov 2010 02:27:26 -0700 [thread overview]
Message-ID: <EE766BAE-E930-46EB-BB89-FE83C7597169@sb.org> (raw)
In-Reply-To: <AANLkTim0N99M488k3vR5zVDkZv7Wz-08hRwdy0jaHh4c@mail.gmail.com>
On Nov 4, 2010, at 2:26 AM, Ævar Arnfjörð Bjarmason wrote:
> On Thu, Nov 4, 2010 at 01:58, Kevin Ballard <kevin@sb.org> wrote:
>> Using "svnadmin hotcopy" you could certainly get your own local repo, but I fail to
>> see how you could easily join your history up with someone else's history using this
>> mechanism. If you really want to use SVN in a distributed manner, I would recommend
>> you simply use SVK.
>
> SVK gives you *disconnected* SVN, not distributed. You still can't
> (easily) share your
> uncommited revisions with others. It just solves the problem of you
> being on a plane
> for a few hours. It doesn't turn SVN into Git.
SVK bills itself as providing distributed patches, and calls itself "A Distributed
Version Control System". I do agree that it's mainly useful for using SVN in a
disconnected mode, but I trust that there's at least some facility for sharing
local branches with other SVK users, though I've certainly never done that myself.
-Kevin Ballard
next prev parent reply other threads:[~2010-11-04 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 0:45 can subversion 1.6 be made "just as distributed as git"? MDellerus
2010-11-04 0:58 ` Kevin Ballard
2010-11-04 8:44 ` Matthieu Moy
2010-11-04 9:26 ` Ævar Arnfjörð Bjarmason
2010-11-04 9:27 ` Kevin Ballard [this message]
2010-11-04 10:00 ` Jakub Narebski
2010-11-04 9:35 ` Ævar Arnfjörð Bjarmason
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=EE766BAE-E930-46EB-BB89-FE83C7597169@sb.org \
--to=kevin@sb.org \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=mdellerus@yahoo.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