best practice for maintaining two differents codes in one mercurial repository

[Bob Hood]

You can use bookmarks if the change is something considered "temporary" and 
will eventually be merged back into the system, or, as Nathan points out, you 
can use named branches if you planto keep the work going in perpetuity, or you 
want to retain the final result for historical reasons.

I personally am of the named branch ilk.  I like the clear separation, and 
with a commercial product, having a distinct and pristine branch available to 
create patches from, or to diagnose customer issues with, has always been of 
greater benefit than the oft lamented polluting of the repository namespace 
that some people seem to abhor.

We keep the 'default' (main) branch as the project do-whatcha-want sandbox, 
and then refine that into separate named branches as we develop feature 
releases.  We also use named branches for private developer work, which is 
vetted by our testing staff before being merged to the feature branch.  Make 
testing and QA just cleaner.


On 6/10/2016 1:19 PM, Nathan Goldbaum wrote:
> You could use two subfolders in the same project. You could also use two 
> named branches.
>
> On Fri, Jun 10, 2016 at 6:16 AM, Hedieh Ebrahimi <hemla21 at gmail.com 
> <mailto:hemla21 at gmail.com>>wrote:
>
>     Dear all,
>
>     I am currently working on two different sub-project. Till now I have had
>     two different mercurial repositories for each. I would like to keep the
>     project all in one repository, but then I still would like to be able to
>     work on the two project simultaneously and separately without having to
>     commit changes from both sub-projects all in one commit. My two
>     sub-projects are totally independent.
>
>     I was wondering what is the best practice in this case.
>
>     Thank you very much in Advance for your help,
>
>     _______________________________________________
>     Mercurial mailing list
>     Mercurial at mercurial-scm.org <mailto:Mercurial at mercurial-scm.org>
>     https://www.mercurial-scm.org/mailman/listinfo/mercurial
>
>
>
>
> _______________________________________________ Mercurial mailing list 
> Mercurial at mercurial-scm.org 
> https://www.mercurial-scm.org/mailman/listinfo/mercurial

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20160610/74a9419d/attachment-0002.html>