creating a branch and subrepos

[Martin Geisler]

Adam Downer <Adam.Downer at monitisegroup.com> writes:

>> I think it's more a question of whether the subrepos follow the same
>> named > branching policy as the parent repo. In cases where a subrepo
>> is shared between multiple parent projects, which may each use their
>> own branch naming policy, it almost would almost never make sense to
>> do this.
>
>> Colin
>
> Unfortunately, I would advocate the almost the exact opposite. But I
> am certain that what I am suggesting would cater for both scenarios.
>
> So, if I were to create a branch in the parent repo but commits to sub
> repos were still on the default branches, then that means when
> developers make changes for other features, by default, the code will
> be mixed up in the default branch of the sub repos and may quickly
> render either development effort inoperable.
>
> My main point is that if I have a set of repositories which I need to
> branch in order to make changes for a new feature. I will need to
> branch each one individually even though they have been collected as
> sub repos in a parent repo.

Yes, doing 'hg branch' inside each subrepo makes a lot of sense if you
are going to touch all those subrepos when developing your feature.

However, if you use the subrepos to track an external dependency without
changing it, then branching that and making an empty commit the next
time you commit the outer repository seems silly.

You even cannot always know which case you are in when you do branch the
outer repository.

-- 
Martin Geisler

Mercurial links: http://mercurial.ch/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20100827/0b89dd0b/attachment.asc>