Putting everything in one repo means that you can have atomic commits that cross modules. This was really painful before and was the primary rationale for the move. -- Yehuda
On Tue, Dec 30, 2008 at 7:09 AM, Simon Chiang <[email protected]>wrote: > > Hey, I'm working on splitting out the tap framework into merbish > modules (ie tap-core, tap-gen, tap...) and I wanted to know your > opinion about stacking all the merb submodules into a single git > repo. It looks like at one time you had a separate git repository for > each module, but then you aggregated them all into wycats/merb. > > I'm assuming there is some benefit to going the aggregate way... is it > because it's easier to conceptualize what's in merb because it's all > there? Or maybe because it's just easier to checkout? Or something > more subtle? > > Thanks, > > - Simon > http://github.com/bahuvrihi/tap/tree/master > > > > -- Yehuda Katz Developer | Engine Yard (ph) 718.877.1325 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
