best practice for maintaining two differents codes in one mercurial repository

Hedieh Ebrahimi hemla21 at gmail.com
Mon Jun 13 08:23:48 UTC 2016


Nathan,

Thanks for your reply. So the project I work on has two different
sub-projects each containing a different code. (python and fortran). I can
put the two sub-projects in different folders in one repository, but then
the changeset logs of  two sub-projects will be shown together.

As I understood if I want to have different chain of logs for each of the
sub-projects, then I should create two branches and do development for each
sub-project on a different branch.  I am just wondering if this is the best
way to go or there are better ways?

Thanks for your comments,

On Fri, Jun 10, 2016 at 9:19 PM, Nathan Goldbaum <nathan12343 at gmail.com>
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>
> 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
>> https://www.mercurial-scm.org/mailman/listinfo/mercurial
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20160613/8203be99/attachment-0002.html>


More information about the Mercurial mailing list