A thought on subrepos
Matt Mackall
mpm at selenic.com
Thu Apr 14 16:07:18 CDT 2011
On Thu, 2011-04-14 at 22:41 +0200, Patrick Mézard wrote:
> Le 14/04/11 22:00, Matt Mackall a écrit :
> > It seems many projects with subrepos are structured like:
> >
> > app/ <- main repo
> > lib/ <- a subrepo
> >
> > This is perhaps the most obvious way to do things, but is not really
> > ideal. A better way is:
> >
> > build/ <- main repo
> > app/ <- subrepo
> > lib/ <- subrepo
> >
> > For starters, this does away with most of the "I didn't mean to
> > recursively commit" issues as commits at the top-level will be much less
> > common.
>
> Why? Am I supposed to work in app/ in this model or ?
Generally, you'll either want to commit in app/ or lib/, and only in
build/ when you've got "synchronization points" - dependencies between
app and lib, releases, etc.
--
Mathematics is the supreme nostalgia of our time.
More information about the Mercurial-devel
mailing list