Re: Modifying Mozilla code on a separate Hg repo?

Benjamin Smedberg <[email protected]> Tue, 20 May 2008 13:55:34 -0400
Newsgroups gmane.comp.mozilla.documentation
Message-ID <[email protected]>
Alex Vincent wrote:
> Benjamin Smedberg wrote:
>  > What are you actually trying to do? Track changes to the 1.9.0.x
>> codebase?
> 
> Yes, exactly - while maintaining my own code changes as well.

So... I don't think you want to use mozilla-central or cvs-trunk-mirror for 
this. cvs-trunk-mirror is not going to be maintained past RC1, and 
mozilla-central will diverge from the 1.9.0.x branch.

Instead, if you want to use mercurial, you should:

* take a Firefox source tarball (say, RC1) and unpack it
* create a new hg repository in that directory (using hg init)
* commit your customizations
* when a new Firefox is released:
** hg update to your Firefox RC1 revision
** unpack the new tarball
** commit the new sources
** hg merge to merge your changes

Make sense?

ASCII-art graph:

Firefox3RC1-->Firefox3RC2-->Firefox3.0.1
       \                \               \
     FF3RC1+custom-->FF3RC2+custom-->FF301+custom

--BDS