[SciPy-dev] The future of SciPy and its development infrastructure
Mon Feb 23 16:59:25 CST 2009
> On Mon, Feb 23, 2009 at 9:46 PM, Charles R Harris
> <firstname.lastname@example.org> wrote:
>> On Mon, Feb 23, 2009 at 2:27 PM, Robert Kern <email@example.com> wrote:
>>> On Mon, Feb 23, 2009 at 15:19, Charles R Harris
>>> <firstname.lastname@example.org> wrote:
>>>> On Mon, Feb 23, 2009 at 2:11 PM, Robert Kern <email@example.com>
>>>>> On Mon, Feb 23, 2009 at 15:06, Charles R Harris
>>>>> <firstname.lastname@example.org> wrote:
>>>>>> I think git-svn takes care of most of the branching problem on a
>>>>>> basis. Where it fall down, IMHO, is in testing a branch on the
>>>>>> sharing a branch among two or three people.
>>>>> Why is that? Push your git branch to github.
>>>> Does github work with our buildbots?
>>> Probably not right now. But that's exactly the same problem if the
>>> main repo were a git one, too.
>> True enough, I'm not arguing for changing the main repository, just pointing
>> out what I miss when making branches locally with git-svn.
> Watching this discussion with interest... Although git seems to have
> more momentum here, I though I would point out bzr-svn, which I think
> allows distributed collaboration around a central svn-hosted branch
> without the problems people have mentioned with git-svn. By storing
> the bzr metadata in svn properties, a full bazaar branch can be hosted
> in svn, so people can branch off it, merge with each other, merge back
> In my experience it's worked very well for giving the distributed
> benefits of branching from a centralised svn repo.
Robin, can you point us to a public svn repo where non-trivial branching
is happening with bzr? I had lots of trouble trying to get anything
working in my attempts.
More information about the Scipy-dev