[haiku-development] Re: Finally deciding on a new source control system for Haiku
- From: Sean Healy <jalopeura@xxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 1 May 2011 06:57:52 +0100
> On Sat, Apr 30, 2011 at 4:34 PM, Sean Healy <jalopeura@xxxxxxxxxxx>
> wrote:
> Well you may be in the minority of students who have experience with
> SVN. So it could be argued that learning Git or Mercurial (hg) would
> not be that much harder than learning SVN for those with no
> experience
> in any of those tools. On the other side of the equation some of the
> other students may already be familiar with Git or Mercurial as well
> as SVN.
> Thanks for your perspective. I'd be interested in hearing from other
> GSoC students in whether switching now would make things more
> difficult for them.
This is a good point. I returned to school after working for several
years, and it is very possible that the younger students are working
with something newer.
> I am curious what the plan is for GSoC student's code. I think in the
> past we made Subversion branches for students to work in. Though
> sometimes their work remains lost in those branches if no one takes
> the time to merge them in (though that is no argument against SVN
> since the same could happen with any tool.) I know in some cases
> students just made their own repos in other places, which I think is
> a
> bit silly when the Haiku project should be able to provide a place
> for
> them to work.
When I first submitted my idea (two years ago), I created a OSDrawer
project for it, since it was not envisioned that it would be part of
the codebase of Haiku itself. I have not heard whether the plan is now
to create a branch for me. It may very well be that I do not end up
working within the Haiku repository in any case.
Other related posts:
