From: "Branko Čibej" <brane@wandisco.com>
To: dev@subversion.apache.org
Cc: "Eric S. Raymond" <esr@thyrsus.com>, git@vger.kernel.org
Subject: Re: reposurgeon now writes Subversion repositories
Date: Thu, 29 Nov 2012 11:31:49 +0100 [thread overview]
Message-ID: <50B73995.5050505@wandisco.com> (raw)
In-Reply-To: <20121129075829.GE3424@lp-shahaf.local>
On 29.11.2012 08:58, Daniel Shahaf wrote:
> I think you're saying that adds might turn into copies, and
> vice-versa. That is something users would notice --- it is certainly
> exposed in the UI --- even though node-id's are not exposed to clients.
... yet. But there are plans underway to expose them.
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
next prev parent reply other threads:[~2012-11-29 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 5:59 reposurgeon now writes Subversion repositories Eric S. Raymond
2012-11-29 7:58 ` Daniel Shahaf
2012-11-29 10:31 ` Branko Čibej [this message]
2012-11-29 11:46 ` Eric S. Raymond
2012-11-29 13:42 ` Daniel Shahaf
2012-11-29 13:55 ` Eric S. Raymond
2012-11-29 13:43 ` AW: " Markus Schaber
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=50B73995.5050505@wandisco.com \
--to=brane@wandisco.com \
--cc=dev@subversion.apache.org \
--cc=esr@thyrsus.com \
--cc=git@vger.kernel.org \
/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).