Handling thirdparty 'vendor' branches
Giorgos Keramidas
keramida at ceid.upatras.gr
Sat Jul 12 04:28:04 CDT 2008
On Sat, 12 Jul 2008 08:42:03 +0200, "Peter Arrenbrecht" <peter.arrenbrecht at gmail.com> wrote:
>> That's amazing. It's _exactly_ what I wanted Hg to do. To track the
>> rename of the vendor code only in the 'target' tree, and then DTRT when
>> merges need to touch/affect files in the target tree. Fantastic :)
>
> Hmm. You should just be aware that Hg has no cheap renames. You
> essentially double the repo size of the vendor branch in your local
> repo. Maybe tracking the vendor branch as an `hg branch` directly
> within the main repo in the proper location would suffice? Really
> depends on the size and compressibility of the vendor code being
> brought in. If, for example, it's a bunch of big .jars, the
> duplication may be rather noticeable.
That's a good point, thanks :)
Duplicating the size of each vendor branch sounds a bit evil.
More information about the Mercurial
mailing list