On Thu, Dec 25, 2008 at 9:50 PM, tropperstyle <[email protected]>wrote:
> > My first resource to get a good overview of git was the peepcode > screen cast: http://peepcode.com/products/git. It covers everything > from installation, configuration, branches, philosophy, > repositories....everything. > > The man pages are also very helpful for getting an overview of each > command. > > I would just recommend installing git, search for an open source > project you are interested in on github.com, checkout the repo and > play around with the commands. You will be surprised how incredibly > intuitive it is. I tried to get used with Git for a day, and I see the advantages. However, at this point, to me, it completely fails to provide a intuitive client. It might be nice for the shell geeks, but unless there isn't a full featured windows client around, we can't make the switch. I'd love to know if there's something in the works, like TortoiseSVN for Git, or at least a seperated client like SmartSVN. > > > > > On Dec 22, 2:24 am, "Paul Bakaus" <[email protected]> wrote: > > On Sun, Dec 14, 2008 at 7:41 PM, tropperstyle <[email protected] > >wrote: > > > > > > > > > > > > > Just read the latest blog post with all the updates for 1.6. Very > > > excited to see the active progress! One thing that I feel would help > > > exposure and to increase outsiders to submit patches and possible > > > commits is to make the switch from SVN/GoogleCode to GitHub + > > > Lighthouse. Just look at the Rails project, since the switch, there > > > has been a massive influx of people deciding to help out and submit > > > their patches for review and thus the project has become better and > > > more stable overall. Check out Ryan Bate's screen cast to see how easy > > > it is to submit at patch. Fastforward to 8:00 if you want to skip all > > > the rails talk and just see the commit process. > > >http://media.railscasts.com/videos/113_contributing_to_rails_with_git. > .. > > > > > Other that breaking down the barriers for people to commit, I noticed > > > 1.6 is going through a lot of stripping, adding, and re-factoring. Git > > > will make it SO much easier to manage these commits and you can always > > > keep your focus on code. jQuery has gotten a lot of adoption and > > > attention from the rails and merb community, so there is massive > > > amount of good coders who are willing to submit patches that you can > > > tap into by making the switch. > > > > > I was a long time SVN user and now I cannot see how any one would > > > possible not want to make the switch! What are your thoughts, dev team? > > > > Hi there, > > > > I think switching to git is an overall good idea, but I simply don't have > > the > > knowledge of Git yet to safely make the switch. Is there any good > resources > > for me to learn more about it? > > > > Also, it's too late for making the switch for 1.6, but for 1.7, with some > > help > > we could definitely get it going. > > > > > > > > -- > > Paul Bakaus > > UI Architect > > --http://paulbakaus.comhttp://www.linkedin.com/in/paulbakaus > > > -- Paul Bakaus UI Architect -- http://paulbakaus.com http://www.linkedin.com/in/paulbakaus --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery UI" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jquery-ui?hl=en -~----------~----~----~----~------~----~------~--~---
