Plans to change to Git?

classic Classic list List threaded Threaded
50 messages Options
123
Reply | Threaded
Open this post in threaded view
|

Plans to change to Git?

danielku15
Hi Nicolas and other Developers.

Since the time of distributed version control systems SVN is quite out of date. I really love the concept of Git and the idea of the platform Github ("social coding") is simply awesome. Are there any plans that haXe will change it's source code to git?

Using git it is a lot simpler for other developers to follow and contribute to the development of haXe itself. A major difference between SVN and git is the way you commit.

In SVN you have to commit into a remote repository (google code). If you do a lot of changes locally you aren't able to commit till you're done. This means you have to work on an uncommited working copy till you have your work done.  

Using git you can commit into a local copy of the repository. That means you can work and commit each change you've done. Nevermind that the changes aren't finished yet! After you have your work done you can "push" your changes to the remote repository (i.E. Github) and all your changes are available to the public.

If you would move over to Github we could watch your development a lot easier because on Github you can "watch" repostiories. That means you can easily follow all changes of the project (commited changes, issues, etc.). What about contribution? An awesome system. With a single click a developer can fork your repository into his account. That means he gets an own remote clone of the haXe repository. In this repository he can make any bugfixes he want to contribute. After he has done it's work the user can change you a "pull request". That means he provides the new commits to you. You can review and comment on this pull requests and apply them to the original repository with one click.

This are only two improvements you would get by using git. There are a lot of Git-Introductions and Articles out there. Give it a look and let me hear what you think :D

I'd really love to hear the news that haXe starts using git/github.

Cheers
Daniel
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

KaalH!
+1

Le 31 août 2011 à 08:56, danielku15 a écrit :

> Hi Nicolas and other Developers.
>
> Since the time of distributed version control systems SVN is quite out of
> date. I really love the concept of Git and the idea of the platform Github
> ("social coding") is simply awesome. Are there any plans that haXe will
> change it's source code to git?
>
> Using git it is a lot simpler for other developers to follow and contribute
> to the development of haXe itself. A major difference between SVN and git is
> the way you commit.
>
> In SVN you have to commit into a remote repository (google code). If you do
> a lot of changes locally you aren't able to commit till you're done. This
> means you have to work on an uncommited working copy till you have your work
> done.  
>
> Using git you can commit into a local copy of the repository. That means you
> can work and commit each change you've done. Nevermind that the changes
> aren't finished yet! After you have your work done you can "push" your
> changes to the remote repository (i.E. Github) and all your changes are
> available to the public.
>
> If you would move over to Github we could watch your development a lot
> easier because on Github you can "watch" repostiories. That means you can
> easily follow all changes of the project (commited changes, issues, etc.).
> What about contribution? An awesome system. With a single click a developer
> can fork your repository into his account. That means he gets an own remote
> clone of the haXe repository. In this repository he can make any bugfixes he
> want to contribute. After he has done it's work the user can change you a
> "pull request". That means he provides the new commits to you. You can
> review and comment on this pull requests and apply them to the original
> repository with one click.
>
> This are only two improvements you would get by using git. There are a lot
> of Git-Introductions and Articles out there. Give it a look and let me hear
> what you think :D
>
> I'd really love to hear the news that haXe starts using git/github.
>
> Cheers
> Daniel
>
> --
> View this message in context: http://haxe.1354130.n2.nabble.com/Plans-to-change-to-Git-tp6745378p6745378.html
> Sent from the Haxe mailing list archive at Nabble.com.
>
> --
> haXe - an open source web programming language
> http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Quickform | Marcus Bergstrom
In reply to this post by danielku15
+1

Marcus Bergstrom
[hidden email]

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

clemos
In reply to this post by KaalH!
+1 github !

On Wed, Aug 31, 2011 at 11:24 AM, KaalH! <[hidden email]> wrote:

> +1
>
> Le 31 août 2011 à 08:56, danielku15 a écrit :
>
>> Hi Nicolas and other Developers.
>>
>> Since the time of distributed version control systems SVN is quite out of
>> date. I really love the concept of Git and the idea of the platform Github
>> ("social coding") is simply awesome. Are there any plans that haXe will
>> change it's source code to git?
>>
>> Using git it is a lot simpler for other developers to follow and contribute
>> to the development of haXe itself. A major difference between SVN and git is
>> the way you commit.
>>
>> In SVN you have to commit into a remote repository (google code). If you do
>> a lot of changes locally you aren't able to commit till you're done. This
>> means you have to work on an uncommited working copy till you have your work
>> done.
>>
>> Using git you can commit into a local copy of the repository. That means you
>> can work and commit each change you've done. Nevermind that the changes
>> aren't finished yet! After you have your work done you can "push" your
>> changes to the remote repository (i.E. Github) and all your changes are
>> available to the public.
>>
>> If you would move over to Github we could watch your development a lot
>> easier because on Github you can "watch" repostiories. That means you can
>> easily follow all changes of the project (commited changes, issues, etc.).
>> What about contribution? An awesome system. With a single click a developer
>> can fork your repository into his account. That means he gets an own remote
>> clone of the haXe repository. In this repository he can make any bugfixes he
>> want to contribute. After he has done it's work the user can change you a
>> "pull request". That means he provides the new commits to you. You can
>> review and comment on this pull requests and apply them to the original
>> repository with one click.
>>
>> This are only two improvements you would get by using git. There are a lot
>> of Git-Introductions and Articles out there. Give it a look and let me hear
>> what you think :D
>>
>> I'd really love to hear the news that haXe starts using git/github.
>>
>> Cheers
>> Daniel
>>
>> --
>> View this message in context: http://haxe.1354130.n2.nabble.com/Plans-to-change-to-Git-tp6745378p6745378.html
>> Sent from the Haxe mailing list archive at Nabble.com.
>>
>> --
>> haXe - an open source web programming language
>> http://haxe.org
>
>
> --
> haXe - an open source web programming language
> http://haxe.org
>

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Yanis Benson
In reply to this post by danielku15

+1

On 31 Aug 2011 10:57, "danielku15" <[hidden email]> wrote:
> Hi Nicolas and other Developers.
>
> Since the time of distributed version control systems SVN is quite out of
> date. I really love the concept of Git and the idea of the platform Github
> ("social coding") is simply awesome. Are there any plans that haXe will
> change it's source code to git?
>
> Using git it is a lot simpler for other developers to follow and contribute
> to the development of haXe itself. A major difference between SVN and git is
> the way you commit.
>
> In SVN you have to commit into a remote repository (google code). If you do
> a lot of changes locally you aren't able to commit till you're done. This
> means you have to work on an uncommited working copy till you have your work
> done.
>
> Using git you can commit into a local copy of the repository. That means you
> can work and commit each change you've done. Nevermind that the changes
> aren't finished yet! After you have your work done you can "push" your
> changes to the remote repository (i.E. Github) and all your changes are
> available to the public.
>
> If you would move over to Github we could watch your development a lot
> easier because on Github you can "watch" repostiories. That means you can
> easily follow all changes of the project (commited changes, issues, etc.).
> What about contribution? An awesome system. With a single click a developer
> can fork your repository into his account. That means he gets an own remote
> clone of the haXe repository. In this repository he can make any bugfixes he
> want to contribute. After he has done it's work the user can change you a
> "pull request". That means he provides the new commits to you. You can
> review and comment on this pull requests and apply them to the original
> repository with one click.
>
> This are only two improvements you would get by using git. There are a lot
> of Git-Introductions and Articles out there. Give it a look and let me hear
> what you think :D
>
> I'd really love to hear the news that haXe starts using git/github.
>
> Cheers
> Daniel
>
> --
> View this message in context: http://haxe.1354130.n2.nabble.com/Plans-to-change-to-Git-tp6745378p6745378.html
> Sent from the Haxe mailing list archive at Nabble.com.
>
> --
> haXe - an open source web programming language
> http://haxe.org

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Danny Wilson
+1

Github also allows you to edit a file online and create a pull request
directly.  So if you spot a typo, or want to add documentation while
browsing the code it's literally 10 seconds of work to supply a patch!

I've switched to git since 2007 - windows support has improved alot
since then.


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Juan Delgado
Github all the way!

On Wed, Aug 31, 2011 at 11:47 AM, Danny Wilson <[hidden email]> wrote:

> +1
>
> Github also allows you to edit a file online and create a pull request
> directly.  So if you spot a typo, or want to add documentation while
> browsing the code it's literally 10 seconds of work to supply a patch!
>
> I've switched to git since 2007 - windows support has improved alot since
> then.
>
>
> --
> haXe - an open source web programming language
> http://haxe.org
>



--
Juan Delgado - Zárate
http://zarate.tv
http://blog.zarate.tv

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

sledorze
In reply to this post by danielku15
+1
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Nemea Lion
In reply to this post by danielku15
+1

2011/8/31 danielku15 <[hidden email]>
Hi Nicolas and other Developers.

Since the time of distributed version control systems SVN is quite out of
date. I really love the concept of Git and the idea of the platform Github
("social coding") is simply awesome. Are there any plans that haXe will
change it's source code to git?

Using git it is a lot simpler for other developers to follow and contribute
to the development of haXe itself. A major difference between SVN and git is
the way you commit.

In SVN you have to commit into a remote repository (google code). If you do
a lot of changes locally you aren't able to commit till you're done. This
means you have to work on an uncommited working copy till you have your work
done.

Using git you can commit into a local copy of the repository. That means you
can work and commit each change you've done. Nevermind that the changes
aren't finished yet! After you have your work done you can "push" your
changes to the remote repository (i.E. Github) and all your changes are
available to the public.

If you would move over to Github we could watch your development a lot
easier because on Github you can "watch" repostiories. That means you can
easily follow all changes of the project (commited changes, issues, etc.).
What about contribution? An awesome system. With a single click a developer
can fork your repository into his account. That means he gets an own remote
clone of the haXe repository. In this repository he can make any bugfixes he
want to contribute. After he has done it's work the user can change you a
"pull request". That means he provides the new commits to you. You can
review and comment on this pull requests and apply them to the original
repository with one click.

This are only two improvements you would get by using git. There are a lot
of Git-Introductions and Articles out there. Give it a look and let me hear
what you think :D

I'd really love to hear the news that haXe starts using git/github.

Cheers
Daniel

--
View this message in context: http://haxe.1354130.n2.nabble.com/Plans-to-change-to-Git-tp6745378p6745378.html
Sent from the Haxe mailing list archive at Nabble.com.

--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

T-Lemon
In reply to this post by danielku15
+1.

2011/8/31 danielku15 <[hidden email]>
Hi Nicolas and other Developers.

Since the time of distributed version control systems SVN is quite out of
date. I really love the concept of Git and the idea of the platform Github
("social coding") is simply awesome. Are there any plans that haXe will
change it's source code to git?

Using git it is a lot simpler for other developers to follow and contribute
to the development of haXe itself. A major difference between SVN and git is
the way you commit.

In SVN you have to commit into a remote repository (google code). If you do
a lot of changes locally you aren't able to commit till you're done. This
means you have to work on an uncommited working copy till you have your work
done.

Using git you can commit into a local copy of the repository. That means you
can work and commit each change you've done. Nevermind that the changes
aren't finished yet! After you have your work done you can "push" your
changes to the remote repository (i.E. Github) and all your changes are
available to the public.

If you would move over to Github we could watch your development a lot
easier because on Github you can "watch" repostiories. That means you can
easily follow all changes of the project (commited changes, issues, etc.).
What about contribution? An awesome system. With a single click a developer
can fork your repository into his account. That means he gets an own remote
clone of the haXe repository. In this repository he can make any bugfixes he
want to contribute. After he has done it's work the user can change you a
"pull request". That means he provides the new commits to you. You can
review and comment on this pull requests and apply them to the original
repository with one click.

This are only two improvements you would get by using git. There are a lot
of Git-Introductions and Articles out there. Give it a look and let me hear
what you think :D

I'd really love to hear the news that haXe starts using git/github.

Cheers
Daniel

--
View this message in context: http://haxe.1354130.n2.nabble.com/Plans-to-change-to-Git-tp6745378p6745378.html
Sent from the Haxe mailing list archive at Nabble.com.

--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

bruno baudry
-1
why ?
1 - I'm french and frenchs allways moarn, complain and say the opposite of what everybody says !
2 - SVN work pretty cool as is and i don't see how it'll improve haxe's addoption and/or anybody's workflow
3 - I've been reading some twits, of some gurus theses days, complainning of GIT messing up with the code... (can't prove it though).
4 - obviously had time to waste today ;)


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Elsass Philippe
In reply to this post by danielku15
So many people saying +1 for GIT...

Let me guess how many of you are actually going to contribute patches to haxe.

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

bruno baudry
Damm ! that was my 5th ;)

2011/8/31 Elsass Philippe <[hidden email]>
So many people saying +1 for GIT...

Let me guess how many of you are actually going to contribute patches to haxe.

--
haXe - an open source web programming language
http://haxe.org



--
_      _  _     _  _\   /
|_)    |_)|_||  || \ |_)Y
|_)    |_)|  ||_||_/|  \ |

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

singmajesty
In reply to this post by Elsass Philippe
+1


On Wed, 31 Aug 2011 08:37:54 -0700, Elsass Philippe  
<[hidden email]> wrote:

> So many people saying +1 for GIT...
>
> Let me guess how many of you are actually going to contribute patches to
> haxe.


--
Using Opera's revolutionary email client: http://www.opera.com/mail/

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Dion Whitehead Amago
In reply to this post by bruno baudry
+1

On Wed, Aug 31, 2011 at 10:59 AM, bruno baudry <[hidden email]> wrote:

> Damm ! that was my 5th ;)
>
> 2011/8/31 Elsass Philippe <[hidden email]>
>>
>> So many people saying +1 for GIT...
>> Let me guess how many of you are actually going to contribute patches to
>> haxe.
>> --
>> haXe - an open source web programming language
>> http://haxe.org
>
>
>
> --
> _      _  _     _  _\   /
> |_)    |_)|_||  || \ |_)Y
> |_)    |_)|  ||_||_/|  \ |
>
> --
> haXe - an open source web programming language
> http://haxe.org
>

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

danielku15
In reply to this post by bruno baudry
@Elsass Philippe
Maybe that simply the problem: It's probably to complicated to contribute anything. With Github you have an easy possibility to contribute (Pull Request, Online Editing) and follow projects (News Feeds). That's why they call it "social coding".

With SVN you do not have the possibility to "try something out". If you want to make some bigger changes (like Cauê did with the new targets) you simply cannot commit your WIP anywhere unless you make your own copy on your SVN server. With git you get a clone of the repo and develop the changes into your local repository (or/and commit it to your fork on Github). The developers of haXe immediatly see that you have made a fork and made some cool changes. After you are finished you send a pull request and merge it back to the original repo.

Think of this scenario: haXe is on Github. Cauê wants to develop the C# and Java targets. He makes a fork and starts developing the targets on his "repo copy". People can follow him and watch what he's doing and can start contributing to him. After he's finished he send's a pull request to haXe and they can merge it back to their system and make a new release haXe 3.0.

Currently the code is quite at a hidden place in Google Code (my opinion). Github is a lot more focused on providing the code and share it with everyone as a social (coding) network.

@Bruno Baudry
1 - I can't really counter that argument xD
2 - You probably have to read some theory about git, then you'll se how it will improve the workflows. In SVN you have the workflow: develop into the local working copy, commit it directly to the central SVN server. In git you have this workflow: You develop into your local working copy and commit it to your local repository. After you have finished your work you push (upload) your work to the (logical) central repository. But in addition SVN simply provides a lot of great features. (branching / merging is a lot easier).
3 - Can't follow that. You can mess up your code with any version control system if you know how. But if you don't play around with "deleting commits" (which is possible in git using special commands) I can't agree with the continus danger of messing up the code. ;)
4 - Read some stuff about git and give it a try. It's worth the time to look at it. If you have tried out your git once, you'll love it and won't get back to SVN.
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Marcelo de Moraes Serpa
+1, git all the way. SVN feels like a big dirty slow and old elephant already. Git Makes it much easier to fork, play around, learn, and finally commit (pull request) something useful to the official repo. 

Nicolas, please consider the move to github.

- M


On Wed, Aug 31, 2011 at 12:39 PM, danielku15 <[hidden email]> wrote:
@Elsass Philippe
Maybe that simply the problem: It's probably to complicated to contribute
anything. With Github you have an easy possibility to contribute (Pull
Request, Online Editing) and follow projects (News Feeds). That's why they
call it "social coding".

With SVN you do not have the possibility to "try something out". If you want
to make some bigger changes (like Cauê did with the new targets) you simply
cannot commit your WIP anywhere unless you make your own copy on your SVN
server. With git you get a clone of the repo and develop the changes into
your local repository (or/and commit it to your fork on Github). The
developers of haXe immediatly see that you have made a fork and made some
cool changes. After you are finished you send a pull request and merge it
back to the original repo.

Think of this scenario: haXe is on Github. Cauê wants to develop the C# and
Java targets. He makes a fork and starts developing the targets on his "repo
copy". People can follow him and watch what he's doing and can start
contributing to him. After he's finished he send's a pull request to haXe
and they can merge it back to their system and make a new release haXe 3.0.

Currently the code is quite at a hidden place in Google Code (my opinion).
Github is a lot more focused on providing the code and share it with
everyone as a social (coding) network.

@Bruno Baudry
1 - I can't really counter that argument xD
2 - You probably have to read some theory about git, then you'll se how it
will improve the workflows. In SVN you have the workflow: develop into the
local working copy, commit it directly to the central SVN server. In git you
have this workflow: You develop into your local working copy and commit it
to your local repository. After you have finished your work you push
(upload) your work to the (logical) central repository. But in addition SVN
simply provides a lot of great features. (branching / merging is a lot
easier).
3 - Can't follow that. You can mess up your code with any version control
system if you know how. But if you don't play around with "deleting commits"
(which is possible in git using special commands) I can't agree with the
continus danger of messing up the code. ;)
4 - Read some stuff about git and give it a try. It's worth the time to look
at it. If you have tried out your git once, you'll love it and won't get
back to SVN.

--
View this message in context: http://haxe.1354130.n2.nabble.com/Plans-to-change-to-Git-tp6745378p6747548.html
Sent from the Haxe mailing list archive at Nabble.com.

--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

danielku15
There was a time everyone used CVS. Then a lot of people moved on to SVN. Nobody likes the people that still use CVS.
Now everybody is moving to Git/Mercurial. Who want's to be like the CVS people and use still SVN? xD
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Alex Liebert
what problem do we currently have, that git is going to solve?

On Wed, Aug 31, 2011 at 11:01 AM, danielku15 <[hidden email]> wrote:
There was a time everyone used CVS. Then a lot of people moved on to SVN.
Nobody likes the people that still use CVS.
Now everybody is moving to Git/Mercurial. Who want's to be like the CVS
people and use still SVN? xD

--
View this message in context: http://haxe.1354130.n2.nabble.com/Plans-to-change-to-Git-tp6745378p6747623.html
Sent from the Haxe mailing list archive at Nabble.com.

--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

danielku15
Git + Github allows easier contribution of code and provides a better communication of changes made to haXe (in code).

There are no problems in Windows XP that are solved with Windows 7. But you all will upgrade some time because it simply is more comfort and provides a lot of additional stuff you'll love.

Of course you can stay at any old system because it works for your needs. But all others who like the new systems have to take care of your old system and use old stuff too. ;)
123