In my opinion, the power of git comes in how easy it is to work with repos, and how cheap they are. All a repo is is just data stored in a .git folder at the top level. If these projects are really separate projects, each one should definitely be its own repo. (A repo for each subfolder).
-- Maksim Pecherskiy mak...@maksimize.com 773.677.7755 @MrMaksimize On Wednesday, August 1, 2012 at 10:26 AM, Dan Luciano wrote: > I am new to Git. I have used Perforce and SourceSafe in the past. My > question is about managing multiple projects using Git. For example, we have > all of our projects in a main folder. This main folder has sub-folders for > each project such as endorsements, rating, business objects, etc. Is it best > to create a repository for the main folder, or should a repository be created > for each sub-folder? What is the "best practice" that others use? > > -- > You received this message because you are subscribed to the Google Groups > "Git for human beings" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/git-users/-/WC2kpFWwVLMJ. > To post to this group, send email to git-users@googlegroups.com > (mailto:git-users@googlegroups.com). > To unsubscribe from this group, send email to > git-users+unsubscr...@googlegroups.com > (mailto:git-users+unsubscr...@googlegroups.com). > For more options, visit this group at > http://groups.google.com/group/git-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
