howto about git and drupal modules maintain
Hello all, I posted a little how to about maintaining drupal modules using git: http://drupal.org/node/288873 I'm sending this email because I see high activity on git related mails. Hope this helps, ________________________________ Marco Antonio Villegas Vega ( __ - __ ) Ing. Informatica http://blog.pucp.edu.pe/marvil07
Hi, This looks really cool. I do all the e-Commerce development in git and esp when working with many branches it is so easy to keep it all in line with different versions. Fixing a bug in 1 very can very easily be copied to another branch, and I find that they will convert 80% of the time with no manual effort. However I don't like the CVS integration as much as I like the SVN integration. The SVN integration work much more like just another git repository and once you have made all the changes you can pass in all the commits at once. it is quite cool. Gordon. On 30/07/2008, at 1:25 PM, Marco Antonio Villegas Vega wrote:
Hello all,
I posted a little how to about maintaining drupal modules using git: http://drupal.org/node/288873
I'm sending this email because I see high activity on git related mails.
Hope this helps, ________________________________
Marco Antonio Villegas Vega ( __ - __ ) Ing. Informatica http://blog.pucp.edu.pe/marvil07 !DSPAM:1000,488fdef1230554881810528!
This looks really good, and may just give me the excuse I've been looking for to get into GIT, as CVS is somewhat of a pain IMO... but what I have yet to see is someone explain the pros and cons. GIT still looks to me like it's just a bunch more commands to try to memorize. Does anyone have some resources that clearly outline why anyone would want to use GIT over CVS or even SVN? Thanks, ~Jerad On Wed, Jul 30, 2008 at 12:57 AM, Gordon Heydon <gordon@heydon.com.au>wrote:
Hi,
This looks really cool.
I do all the e-Commerce development in git and esp when working with many branches it is so easy to keep it all in line with different versions.
Fixing a bug in 1 very can very easily be copied to another branch, and I find that they will convert 80% of the time with no manual effort.
However I don't like the CVS integration as much as I like the SVN integration. The SVN integration work much more like just another git repository and once you have made all the changes you can pass in all the commits at once. it is quite cool.
Gordon.
On 30/07/2008, at 1:25 PM, Marco Antonio Villegas Vega wrote:
Hello all,
I posted a little how to about maintaining drupal modules using git: http://drupal.org/node/288873
I'm sending this email because I see high activity on git related mails.
Hope this helps, ________________________________
Marco Antonio Villegas Vega ( __ - __ ) Ing. Informatica http://blog.pucp.edu.pe/marvil07 !DSPAM:1000,488fdef1230554881810528!
I watched a talk by Linus Lorvalds on Git: http://video.google.com/videosearch?q=linus+git# It's quite entertaining if nothing else. Git seems to have real benefits when lots of people will be working on the same code and there is one moderator deciding what they want to 'pull' into the main branch. CVS is a pain, especially for beginners like me but I feel, since it's necessary for Drupal I just have to get used to it. Here's some information on Git vs SVN: http://git.or.cz/gitwiki/GitSvnComparsion psynaptic http://freestylesystems.co.uk http://api.freestylesystems.co.uk On 30 Jul 2008, at 15:39, Jerad Bitner wrote:
This looks really good, and may just give me the excuse I've been looking for to get into GIT, as CVS is somewhat of a pain IMO... but what I have yet to see is someone explain the pros and cons.
GIT still looks to me like it's just a bunch more commands to try to memorize. Does anyone have some resources that clearly outline why anyone would want to use GIT over CVS or even SVN?
Thanks, ~Jerad
On Wed, Jul 30, 2008 at 12:57 AM, Gordon Heydon <gordon@heydon.com.au>wrote:
Hi,
This looks really cool.
I do all the e-Commerce development in git and esp when working with many branches it is so easy to keep it all in line with different versions.
Fixing a bug in 1 very can very easily be copied to another branch, and I find that they will convert 80% of the time with no manual effort.
However I don't like the CVS integration as much as I like the SVN integration. The SVN integration work much more like just another git repository and once you have made all the changes you can pass in all the commits at once. it is quite cool.
Gordon.
On 30/07/2008, at 1:25 PM, Marco Antonio Villegas Vega wrote:
Hello all,
I posted a little how to about maintaining drupal modules using git: http://drupal.org/node/288873
I'm sending this email because I see high activity on git related mails.
Hope this helps, ________________________________
Marco Antonio Villegas Vega ( __ - __ ) Ing. Informatica http://blog.pucp.edu.pe/marvil07 !DSPAM:1000,488fdef1230554881810528!
On Wed, Jul 30, 2008 at 7:53 AM, Richard Burford <rich@freestylesystems.co.uk> wrote:
CVS is a pain, especially for beginners like me but I feel, since it's necessary for Drupal I just have to get used to it.
CVS seems to still be around simply because no-one is willing to tackle the problem of going to svn or something else. Some other projects are moving away from CVS: Mozilla => Hg PHP => SVN IMHO Drupal could move at least to svn as it is much simpler to learn than CVS and has better tools for people that want to use things like git, hg or bazaar. D7 would have been a good point to do that but it doesn't seem to be a priority for core. Jeff
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeff Griffiths schrieb:
On Wed, Jul 30, 2008 at 7:53 AM, Richard Burford <rich@freestylesystems.co.uk> wrote:
CVS is a pain, especially for beginners like me but I feel, since it's necessary for Drupal I just have to get used to it.
CVS seems to still be around simply because no-one is willing to tackle the problem of going to svn or something else. Some other projects are moving away from CVS:
Mozilla => Hg PHP => SVN
IMHO Drupal could move at least to svn as it is much simpler to learn than CVS and has better tools for people that want to use things like git, hg or bazaar.
Please stop, we've had that discussion more often than I care to count. The gist is: As long as there are no suitable GUIs for dummies there is no point in moving away from CVS. Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIkIaAfg6TFvELooQRArlCAJ4nUpLCnViM6Cvwn85fdXpFu/O3/QCfU3Er /csXDfR0fZB43wtBDu7rdRY= =4zcO -----END PGP SIGNATURE-----
On Wed, Jul 30, 2008 at 9:23 AM, Konstantin Käfer <kkaefer@gmail.com> wrote:
The gist is: As long as there are no suitable GUIs for dummies there is no point in moving away from CVS.
Well, there are quite good GUIs for svn (often better than those for CVS). But we need that and we need someone to take over and really support the version control API so that project/project_issue/project_release modules can be RCS independent (see http://lists.drupal.org/pipermail/development/2008-July/030453.html for a plea for help on this).
And: CVS working copies can be checked into an SVN repository without any problems.
I'm not sure where you were heading with this - perhaps that using CVS for the project makes it easy for all us developers who prefer SVN because we can include CVS into SVN. However, SVN working copies can be "checked into" SVN as well - see external/vendor branches. Regards, Greg -- Greg Knaddison Denver, CO | http://knaddison.com | 303-800-5623 Growing Venture Solutions, LLC | http://growingventuresolutions.com
On Jul 30, 2008, at 8:35 AM, Greg Knaddison - GVS wrote:
Well, there are quite good GUIs for svn (often better than those for CVS).
git can pretend to be a CVS pserver, so I believe you can just use all the CVS clients directly and point them at git.
But we need that and we need someone to take over and really support the version control API so that project/project_issue/project_release modules can be RCS independent (see http://lists.drupal.org/pipermail/development/2008-July/030453.html for a plea for help on this).
That's the heart of the matter. In addition to someone to adopt, fix, maintain and extend the versioncontrol API and the appropriate backend (versioncontrol_git, presumably), the other big hurdle here is that someone also needs to volunteer to be The Main Support Person(tm) for the 100s (1000s) of support questions that are going to be generated as a result of moving to a distributed version control system for the Drupal developer community. I'm not taking that job. Above person also gets to rewrite dozens of handbook pages and keep them current/ accurate. You'll probably want to start giving talks at every DrupalCon about distributed version control, too. ;) Cheers, -Derek (dww)
Sounds like we need more of a task force then a single person, dww :) On Wed, Jul 30, 2008 at 12:50 PM, Derek Wright <drupal@dwwright.net> wrote:
On Jul 30, 2008, at 8:35 AM, Greg Knaddison - GVS wrote:
Well, there are quite good GUIs for svn (often better than those for CVS).
git can pretend to be a CVS pserver, so I believe you can just use all the CVS clients directly and point them at git.
But we need that and we need someone to take over and really support
the version control API so that project/project_issue/project_release modules can be RCS independent (see http://lists.drupal.org/pipermail/development/2008-July/030453.html for a plea for help on this).
That's the heart of the matter.
In addition to someone to adopt, fix, maintain and extend the versioncontrol API and the appropriate backend (versioncontrol_git, presumably), the other big hurdle here is that someone also needs to volunteer to be The Main Support Person(tm) for the 100s (1000s) of support questions that are going to be generated as a result of moving to a distributed version control system for the Drupal developer community. I'm not taking that job. Above person also gets to rewrite dozens of handbook pages and keep them current/accurate. You'll probably want to start giving talks at every DrupalCon about distributed version control, too. ;)
Cheers, -Derek (dww)
On Wed, 2008-07-30 at 09:35 -0600, Greg Knaddison - GVS wrote:
On Wed, Jul 30, 2008 at 9:23 AM, Konstantin Käfer <kkaefer@gmail.com> wrote:
The gist is: As long as there are no suitable GUIs for dummies there is no point in moving away from CVS.
Well, there are quite good GUIs for svn (often better than those for CVS).
But we need that and we need someone to take over and really support the version control API so that project/project_issue/project_release modules can be RCS independent (see http://lists.drupal.org/pipermail/development/2008-July/030453.html for a plea for help on this).
Sorry, jpetso and I never actually did announce over this list, as I immediately took the conversation to one-on-one emails; I imagine the only reason he hasn't responded already is because he's currently on vacation. I offered to take over Version Control API, as well as the rcs-specific extension modules that jpetso was maintainer of (cvs and svn), as long as there wasn't somebody else hot to trot on it. I haven't talked to the maintainers of the hg (ezyang) and git (boombatower) extension modules, but if need be I may step up for those as well once things have moved forward with the API itself. He provided me with a quick-but-effective brain dump about the whole deal prior to his departure, and I've now got quite a lot of information to go on. I don't anticipate that I'll have time to really crack down to it for at least a few weeks, but I am hoping to dig in before Szeged.
And: CVS working copies can be checked into an SVN repository without any problems.
I'm not sure where you were heading with this - perhaps that using CVS for the project makes it easy for all us developers who prefer SVN because we can include CVS into SVN. However, SVN working copies can be "checked into" SVN as well - see external/vendor branches.
Regards, Greg
So my initial note was cryptic and very badly written. My apologies. Here's the point: I've taken over Version Control API from Jakob. I hope to start work with it shortly before Szeged. Sam On Wed, 2008-07-30 at 21:44 -0500, Sam Boyer wrote:
On Wed, 2008-07-30 at 09:35 -0600, Greg Knaddison - GVS wrote:
On Wed, Jul 30, 2008 at 9:23 AM, Konstantin Käfer <kkaefer@gmail.com> wrote:
The gist is: As long as there are no suitable GUIs for dummies there is no point in moving away from CVS.
Well, there are quite good GUIs for svn (often better than those for CVS).
But we need that and we need someone to take over and really support the version control API so that project/project_issue/project_release modules can be RCS independent (see http://lists.drupal.org/pipermail/development/2008-July/030453.html for a plea for help on this).
Sorry, jpetso and I never actually did announce over this list, as I immediately took the conversation to one-on-one emails; I imagine the only reason he hasn't responded already is because he's currently on vacation.
I offered to take over Version Control API, as well as the rcs-specific extension modules that jpetso was maintainer of (cvs and svn), as long as there wasn't somebody else hot to trot on it. I haven't talked to the maintainers of the hg (ezyang) and git (boombatower) extension modules, but if need be I may step up for those as well once things have moved forward with the API itself. He provided me with a quick-but-effective brain dump about the whole deal prior to his departure, and I've now got quite a lot of information to go on. I don't anticipate that I'll have time to really crack down to it for at least a few weeks, but I am hoping to dig in before Szeged.
And: CVS working copies can be checked into an SVN repository without any problems.
I'm not sure where you were heading with this - perhaps that using CVS for the project makes it easy for all us developers who prefer SVN because we can include CVS into SVN. However, SVN working copies can be "checked into" SVN as well - see external/vendor branches.
Regards, Greg
I think most folks are happy to put up with cryptic and badly written if the message is so good ;) thanks for volunteering to maintain that module and for the update. -- Greg Knaddison Denver, CO | http://knaddison.com | 303-800-5623 Growing Venture Solutions, LLC | http://growingventuresolutions.com
Hi, On 31/07/2008, at 1:19 AM, Gerhard Killesreiter wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jeff Griffiths schrieb:
On Wed, Jul 30, 2008 at 7:53 AM, Richard Burford <rich@freestylesystems.co.uk> wrote:
CVS is a pain, especially for beginners like me but I feel, since it's necessary for Drupal I just have to get used to it.
CVS seems to still be around simply because no-one is willing to tackle the problem of going to svn or something else. Some other projects are moving away from CVS:
Mozilla => Hg PHP => SVN
IMHO Drupal could move at least to svn as it is much simpler to learn than CVS and has better tools for people that want to use things like git, hg or bazaar.
Please stop, we've had that discussion more often than I care to count.
The gist is: As long as there are no suitable GUIs for dummies there is no point in moving away from CVS.
Well then we can move to git! We will schedule it for next week ;) git has a CVS server to allow users to use CVS to make commits. So all CVS GUI's work with git. Gordon.
Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIkIaAfg6TFvELooQRArlCAJ4nUpLCnViM6Cvwn85fdXpFu/O3/QCfU3Er /csXDfR0fZB43wtBDu7rdRY= =4zcO -----END PGP SIGNATURE-----
!DSPAM:1000,489089ea257761670870668!
On Wed, 30 Jul 2008 08:02:36 -0700 "Jeff Griffiths" <anisotropic@gmail.com> wrote:
On Wed, Jul 30, 2008 at 7:53 AM, Richard Burford <rich@freestylesystems.co.uk> wrote:
CVS is a pain, especially for beginners like me but I feel, since it's necessary for Drupal I just have to get used to it.
CVS seems to still be around simply because no-one is willing to tackle the problem of going to svn or something else. Some other projects are moving away from CVS:
Mozilla => Hg PHP => SVN
IMHO Drupal could move at least to svn as it is much simpler to learn than CVS and has better tools for people that want to use things like git, hg or bazaar. D7 would have been a good point to do that but it doesn't seem to be a priority for core.
I'm on svn BUT svn is an old tool too. If we are really willing to take the challenge of a change in infrastructure the family of tools to whom git belongs (like bazaar, mercurial, darcs...) could be a good chance to make a longer leap. Don't any of these tools have good GUI for Windows too? -- Ivan Sergio Borgonovo http://www.webthatworks.it
SVN vs Git Centralized vs Decentralized SVN (and CVS) is based on having a centralized repository while Git is decentralized. In SVN, committing, checking out, merging, etc, all need to check into the central (remote) repository. Git's decentralized nature means that all commits, reversions, checkouts, merges, etc, all happen locally. You literally have an entire copy of the repository, entire history and all, and you manually sync up to the central source being used by your team (this is both good and bad depending on your situation). You can do more work without an internet connection than you can with SVN. Since you have to manually sync with the "source control hub" with git, there are extra tools added to be able to manipulate your commits before syncing/pushing out to the hub/public. You can combine commits and rearrange their order to have a clean patch history of each change. The manual syncing also promotes smaller commits because you don't have to worry about breaking someone else's working copy between your commits. A large change can be pushed out instantaneously to your team in a batch of numerous commits. This promotes and encourages people to commit often, helping developers even with their own work. Speed SVN's speed is limited to your network connection. With Git entirely localized, your speed is only limited by your local environment. Internet only comes into the equation when you push your changes to the hub. A merge involving a large amount of files is lightning fast when compared to SVN (I've had checkouts/merges/etc take 20+ minutes). Setting up a repo in Git is also very fast. Since it's decentralized, there is no need for the overhead of creating the centralized location for storage like SVN/CVS. Just "git init" and "git add ." and you're ready to go. Merging Git is designed for the ease of branching and merging. It's goal is that you can maintain multiple branches and merge them with ease. It promotes and encourages the developer to branch because it's so easy. Revisioning SVN uses incremental revisions for the entire repository, trunk, branches, tags and all. Git uses just hashes to identify a unique commit. It thinks more along the lines of "how many commits from HEAD" rather than specific commits. Staging Git has an extra spot between a modified file and a committed change called "staging". This can make it easier to develop, to maintain that "inbetween" spot and not lose your changes. If you've ever copied a file even when working with SVN or CVS, then you'll find staging commits valuable. --- Kathleen Murtagh On Wed, Jul 30, 2008 at 10:39 AM, Jerad Bitner <sirkitree@gmail.com> wrote:
This looks really good, and may just give me the excuse I've been looking for to get into GIT, as CVS is somewhat of a pain IMO... but what I have yet to see is someone explain the pros and cons.
GIT still looks to me like it's just a bunch more commands to try to memorize. Does anyone have some resources that clearly outline why anyone would want to use GIT over CVS or even SVN?
Thanks, ~Jerad
On Wed, Jul 30, 2008 at 12:57 AM, Gordon Heydon <gordon@heydon.com.au> wrote:
Hi,
This looks really cool.
I do all the e-Commerce development in git and esp when working with many branches it is so easy to keep it all in line with different versions.
Fixing a bug in 1 very can very easily be copied to another branch, and I find that they will convert 80% of the time with no manual effort.
However I don't like the CVS integration as much as I like the SVN integration. The SVN integration work much more like just another git repository and once you have made all the changes you can pass in all the commits at once. it is quite cool.
Gordon.
On 30/07/2008, at 1:25 PM, Marco Antonio Villegas Vega wrote:
Hello all,
I posted a little how to about maintaining drupal modules using git: http://drupal.org/node/288873
I'm sending this email because I see high activity on git related mails.
Hope this helps, ________________________________
Marco Antonio Villegas Vega ( __ - __ ) Ing. Informatica http://blog.pucp.edu.pe/marvil07 !DSPAM:1000,488fdef1230554881810528!
You can always watch Linus Torvalds talk about why GIT is wonderful and all the rest suck at Youtube: http://www.youtube.com/watch?v=4XpnKHJAok8 Of course, Linus is not at all opinionated. :-) On Wed, Jul 30, 2008 at 9:39 AM, Jerad Bitner <sirkitree@gmail.com> wrote:
GIT still looks to me like it's just a bunch more commands to try to memorize. Does anyone have some resources that clearly outline why anyone would want to use GIT over CVS or even SVN?
Chris Johnson wrote:
You can always watch Linus Torvalds talk about why GIT is wonderful and all the rest suck at Youtube: http://www.youtube.com/watch?v=4XpnKHJAok8
Of course, Linus is not at all opinionated. :-)
he's earned the right though! -- Sean Burlington www.practicalweb.co.uk
Hi, On 31/07/2008, at 12:39 AM, Jerad Bitner wrote:
This looks really good, and may just give me the excuse I've been looking for to get into GIT, as CVS is somewhat of a pain IMO... but what I have yet to see is someone explain the pros and cons.
For it is the fact that git is a distributed and it is extremely fast.
GIT still looks to me like it's just a bunch more commands to try to memorize. Does anyone have some resources that clearly outline why anyone would want to use GIT over CVS or even SVN?
Again it is distributed. this means that I can commit to my repository anytime I want and I don't need to have access to the internet. The other thing is that it do not have to have commit access to a repository. So if I do some core development, and send in the patch when it gets committed, if someone looks at the commit, it will say that I was the author, and if Dries committed, he is the committer. But also if killes and chx handled the patch they can both sign it to say that it was "inspected by #12" ;) Also branching in git is just the best. it puts CVS's branching to shame. You really start to learn what branching is about. Gordon.
Thanks, ~Jerad
On Wed, Jul 30, 2008 at 12:57 AM, Gordon Heydon <gordon@heydon.com.au> wrote: Hi,
This looks really cool.
I do all the e-Commerce development in git and esp when working with many branches it is so easy to keep it all in line with different versions.
Fixing a bug in 1 very can very easily be copied to another branch, and I find that they will convert 80% of the time with no manual effort.
However I don't like the CVS integration as much as I like the SVN integration. The SVN integration work much more like just another git repository and once you have made all the changes you can pass in all the commits at once. it is quite cool.
Gordon.
On 30/07/2008, at 1:25 PM, Marco Antonio Villegas Vega wrote:
Hello all,
I posted a little how to about maintaining drupal modules using git: http://drupal.org/node/288873
I'm sending this email because I see high activity on git related mails.
Hope this helps, ________________________________
Marco Antonio Villegas Vega ( __ - __ ) Ing. Informatica http://blog.pucp.edu.pe/marvil07
!DSPAM:1000,4890806a256071421416041!
participants (15)
-
Chris Johnson -
Derek Wright -
Gerhard Killesreiter -
Gordon Heydon -
Greg Knaddison - GVS -
Greg＠GrowingVentureSolutions.com
-
Ivan Sergio Borgonovo -
Jeff Griffiths -
Jerad Bitner -
Kathleen Murtagh -
Konstantin Käfer -
Marco Antonio Villegas Vega -
Richard Burford -
Sam Boyer -
Sean Burlington