From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Kevin Ballard <kevin@sb.org>
Cc: MDellerus <mdellerus@yahoo.com>, git@vger.kernel.org
Subject: Re: can subversion 1.6 be made "just as distributed as git"?
Date: Thu, 04 Nov 2010 09:44:01 +0100 [thread overview]
Message-ID: <vpqy699xyum.fsf@bauges.imag.fr> (raw)
In-Reply-To: <BF8EE51A-AFE4-4EBA-82E8-4A8B32678FBF@sb.org> (Kevin Ballard's message of "Wed\, 3 Nov 2010 17\:58\:29 -0700")
Kevin Ballard <kevin@sb.org> writes:
> 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.
Right. Branching is the easy part. Merging is the hard and important
one.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2010-11-04 8:48 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 [this message]
2010-11-04 9:26 ` Ævar Arnfjörð Bjarmason
2010-11-04 9:27 ` Kevin Ballard
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=vpqy699xyum.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=kevin@sb.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