Timeline for How to determine when to open a new branch or a new repository when using Git?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 31, 2015 at 21:37 | history | edited | tamas.kenez | CC BY-SA 3.0 |
remove unimportant, incorrect detail
|
| Dec 31, 2015 at 21:34 | comment | added | tamas.kenez | @Snowman: not the svn way - i think you're right, fixing it... | |
| Dec 31, 2015 at 14:02 | comment | added | user22815 | Keeping all the projects in one repository is not the SVN way: I have seen many times where each project or group of very closely related projects are in their own repositories. Neither SVN nor Git, as a technology, have a "preference" for how to group projects in repositories. The only issue here is separate repositories in Git will be faster if you only need to clone a subset of the total subprojects. | |
| Dec 31, 2015 at 13:55 | history | edited | tamas.kenez | CC BY-SA 3.0 |
minor
|
| Dec 30, 2015 at 18:34 | history | edited | tamas.kenez | CC BY-SA 3.0 |
add bottom line
|
| Dec 30, 2015 at 18:31 | comment | added | tamas.kenez | Yes, you cannot...I guess I should add a bottom line to my answer. | |
| Dec 30, 2015 at 17:51 | comment | added | Eric King | If you use branches to distinguish between each client's distinct version of your product, you cannot 'merge and delete' the branches. They will be perpetual. I think that's what the question is asking: should they be perpetual branches or their own repo? | |
| Dec 30, 2015 at 17:45 | history | answered | tamas.kenez | CC BY-SA 3.0 |