On Jan 3, 2013, at 6:31 PM, Derek Gaston <fried...@gmail.com> wrote: > One of the greatest things about Git is that there are so many ways to setup > your project's work flow. Every project can decide for themselves what will > work best for that project. It's freedom we never had with the old systems. > It's awesome to see all the different way of working with this tool!
One of the things I like about the model described in the link sent out is that it is a convenient way to get back to the "trunk should always work" notion we debated around Thanksgiving. Also, it would allow us to not check in generated files except for master. It looks like after the initial creation, you only push back to master (if "hotfixes" were only created from the develop branch). That would allow for files to exist in master that are not tracked in any other branch, correct? Specifically, if we were to remove generated files from master, create a develop branch, and reintroduce generated files on master, all would be happy? After all, automake 1.13 is out and I've held off annoying everyone with a Makefile.in update for over a week now! ;-) -Ben ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
