On Mon, Nov 17, 2014 at 05:57:53PM -0800, Andrew wrote: > When the branch is finally ready for review it has to be merged with the > latest development branch, so you can't avoid this indefinitely. As with > Nathan, I'm reluctant to continuously switch between versions because of > the compile time lag.
hi there. some thoughts - there is no such thing as a 'reviewed' branch. if a review corresponded to a merge into 'reviewed', no switching back (to develop? master?) would be necessary (in theory..) - git-new-workdir (part of git) [1] permits multiple work directories on top of one repository. this makes multiple builds more efficient, such as one for production and one for review. - aufs [2]. use an overlay for reviewing. afterwards discard it and return to the previous state. hth felix [1] -> search engine, tons of resources available. [2] http://aufs.sourceforge.net -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
