according to your description, your project seems to be something like the
Linux kernel, and Git handles that just fine. Depending on your build
environment, Git branches may help you a lot, as, if it is designed well,
can prevent full rebuilds.
On 19 Oct 2013 23:40, "Blake McBride" <blake1...@gmail.com> wrote:
> I have a large application that takes about two hours to build. Sometime
> I have to do partial-project commits in order to communicate
> development from one area to another (I can explain further but it is
> irrelevant to the question). I'd prefer (if I was using git rather than
> svn) to create a branch to commit the partial work, debug, and finally
> merge to the master when it is all done. This way each commit on masterwould
> be stable (contain no partial commits). My problem is this. Given
> the size of the project, I can't checkout different versions without
> causing a two hour build. I am sure this must be a common problem.
> Stated another way - when you have a very large project, branching becomes
> a significant problem because of build times. Are there common solutions
> to this sort of problem?
> Blake McBride
> 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/groups/opt_out.
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
For more options, visit https://groups.google.com/groups/opt_out.