• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Rob Spoor
  • Junilu Lacar
  • paul wheaton
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Scott Selikoff
Bartenders:
  • Piet Souris
  • Jj Roberts
  • fred rosenberger

Git workflow

 
Greenhorn
Posts: 9
Spring Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
After using SVN for a long time, I am getting pulled into Git through some open source projects that I am helping.

It seems that the Git workflow is very different.

Can you briefly describe the workflow for some of the common use cases where there is a difference between SVN and Git.
 
Video Author
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
One of the fundamental differences between SVN and Git is that Subversion is Centralized. That means there must be a centralized master authority with respect to the codebase.
As you are seeing while you work on Open Source projects, a Distributed SCM - like Git - does not necessarily require one centralize repository. Each user has a complete copy of the entire history and can work independently. Changes can be later merged into those of another developer (GitHub uses the Pull Request as a means to 'request' your changes are included but provides the maintainer ultimate purview over the project). This can even be from one machine to another! Changes (in the form of patches) can be sent via email to be merged into a copy of the Git repository held by another developer.

So, overall the philosophy is "I can work on MY code, protect MY code from others, share MY code as I desire" without the necessity of connection to a master centralized data store. In practice, particularly in the Open Source world, there is a repository understood to be that MASTER. And Git supports that concept easily. This is what has made GitHub so large.

I may not have answered your question directly - about Workflow and Use Cases - but I hope this provides a clearer perspective on how Git "thinks". There may be others here who can offer Case-History stories about particular workflow(s).
 
Ron Wheeler
Greenhorn
Posts: 9
Spring Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

That is a helpful perspective and gives me some ideas about the next steps in a couple of things that I am starting to work on.

Thanks
 
pie. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic