At least not a bad idea. After all, a new branch in git only add one more file under .git/refs directory in which there is only one line recording the commit hash value your branch is pointing to. IMO, you won't be any problems with thousands of branches exist in your project.
On Tue, Apr 14, 2015 at 11:33 PM, leam hall <leamh...@gmail.com> wrote: > Working on a project that's importing code from an older project. There > are 2-3 dozen small bits and we're trying to add some functionality and > clean up the code in each small bit. Would it make sense to make each small > bit it's own branch? The theory is that as each branch becomes workable it > gets merged into master. That way no user pulls code that doesn't work and > gets a bad impression of the project. > > Thoughts? > > -- > 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. > -- 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.
