I think it would be good if you maintain it separately as it would be
easier to keep track. You could of course do the same if you keep it
together. But I personally believe using git diff would become much
easier. And also remember that each commit should only represent 1
logical change. Now suppose you did changed one file in one part, then
it should be commit. Then you might change another file in another
part. And thus when you do git log, you will have to see which file
belongs to which part and then it would become tedious and
unnecessary. And I don't see any harm in maintaining separate

On Friday, 21 August 2015 13:05:04 UTC+5:30, Irakli Lomidze wrote:
> Dear Sirs.
> I have Multiple SKU of my application, (eg Standard, Enterprise, Corporate)
> What is best or suggested git workflow for it. ?
> or I should manage it in separate folders as separate project with 
> individual git standard flow ?
> Thank you in Advance. 

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to