Wierd, any clue as to why?

There are some tools with git though that makes it operate with svn. Like, as in that developers can use all the functions in git locally, but still push/pull to SVN. Might be worth faffing about with and writing a guide? If it works well and doesn't cause major headaches maybe people can use both.

I know the dual repositories are a bitch to maintain and not exactly bug free, but it might be possible for people to use whichever tool fits them best locally?
Actually, now I am itching to try it :).

I just feel like it would lower the entry point significantly for super simple patches and maintenance. But then, I am not a reactos developer ;).

2017-02-15 11:47 GMT+01:00 David Quintana (gigaherz) <gigaherz@gmail.com>:
There was a talk last year, about the possibility of switching. At least one long-time member said if we fully switched, they'd leave the project in bad terms.

On 15 February 2017 at 11:41, Magnus Johnsson <magnusjjj@gmail.com> wrote:
Sure, but, do you know that its a fact? Has anyone checked recently? We are talking vehemently against it here, right, not 'minor annoyance'?
Not calling anyone out here, would just love to hear some input on what they want from the repository system. No pooflinging, promise.

2017-02-15 11:35 GMT+01:00 David Quintana (gigaherz) <gigaherz@gmail.com>:
The number doesn't matter. The ReactOS project can't afford to lost any long-time members. Git would be a benefit for all of us, but it has to be a benefit for ALL of us. SVN works well enough meanwhile, even if passing patch files around is rather 1990s.

On 15 February 2017 at 11:30, Magnus Johnsson <magnusjjj@gmail.com> wrote:
How many developers are we talking about here? :)

2017-02-15 11:19 GMT+01:00 Ged Murphy <gedmurphy.maillists@gmail.com>:

Yeah, I had a meeting about this last week at work. We’re slowly doing the same, pushing all new projects to use tfs git, and give existing projects using vsts the option to convert if they wish.

Git is far better at managing developers working in remote locations, and as most of the software industry has already moved towards devs working remotely, it makes sense. There are very few big companies no longer using a distributed system such as git or mercurial.

 

That fact that open source projects, which are inherently built on devs being remote, are still reluctant to move from a centralized to a distributed system seems archaic and self-detrimental. It’s a shame to hold the project back because a few devs are unwilling to move forward.

 

A distributed system can do everything a centralized system can do if you decide to model it in that way, and so much more if you decide to model it in other ways.

 

Ged.

 

 

From: Ros-dev [mailto:ros-dev-bounces@reactos.org] On Behalf Of David Quintana (gigaherz)
Sent: 15 February 2017 09:57
To: ReactOS Development List <ros-dev@reactos.org>
Subject: Re: [ros-dev] Microsoft switched to Git

 

Unlike us, Microsoft probably doesn't care if a few of the developers would rather quit than switch. ;P

 

On 15 February 2017 at 10:40, Colin Finck <colin@reactos.org> wrote:

https://blogs.msdn.microsoft.com/bharry/2017/02/03/scaling-git-and-some-back-story/

I didn't expect Microsoft to switch to Git sooner than us..

_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

 


_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev


_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev


_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev


_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev


_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev