[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Would branching across repositories be theoretically possible?

From: Ziemowit Laski <zlaski_at_ziemas.net>
Date: Wed, 2 Jan 2013 01:00:13 -0800

Hello everyone,

 

Thank you for all the feedback. I shall now digest it, read up more on
svnsync, git-svn, etc., and then hopefully come up with something
interesting to say.

 

Thanks again,

 

--Zem

 

From: justin.erenkrantz_at_gmail.com [mailto:justin.erenkrantz_at_gmail.com]
On Behalf Of Justin Erenkrantz
Sent: Tuesday, 01 January 2013 18.20
To: Ziemowit Laski; dev_at_subversion.apache.org
Subject: Re: Would branching across repositories be theoretically
possible?

 

On Mon, Dec 31, 2012 at 9:05 AM, Stefan Sperling <stsp_at_apache.org>
wrote:

        BTW, it would have been better to send your question to the
users@ list.

        The dev@ list is off-topic for questions like this. I suppose
you chose
        dev@ because of your idea to develop support for
cross-repository copies,
        which I'll address now:

At a meta-level, I've seen this dismissal and plea to just send to
users@ instead happen a few times recently on dev@. I'd like to ensure
we don't hinder potential contributors by sending out the wrong tone in
their initial interactions with dev@. We welcome all contributors with
open arms. To me, Zem's initial post was perfectly appropriate for dev@
and given the ensuing discussions including some that apparently
happened off-list, it was (and is) a good catalyst for discussion and
bringing those discussions back to the list. In other words, in my
opinion, a very good and on-topic dev@ post.

Back to the topic at hand, my take on this feature is it's probably a
good idea to figure out how to solve it...the landscape over a decade
ago when we started out isn't the same as it is now. -- justin

P.S. Hi Zem! =)
Received on 2013-01-02 10:00:56 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.