Mercurial > kallithea
view docs/usage/subrepos.rst @ 4245:3315e9263a53
Use Conservancy's Kallithea Committee address as author_email.
the setup.py needs an author_email setting. Since this is a fork, the
author_email should be the individuals responsible for the fork. This
address reaches the Kallithea Committee at Conservancy.
author | Bradley M. Kuhn <bkuhn@sfconservancy.org> |
---|---|
date | Fri, 04 Jul 2014 09:40:56 -0400 |
parents | e73a69cb98dc |
children | 03bbd33bc084 |
line wrap: on
line source
.. _subrepos: ============================================= working with Kallithea and mercurial subrepos ============================================= example usage of Subrepos with Kallithea:: ## init a simple repo hg init repo1 cd repo1 echo "file1" > file1 hg add file1 hg ci --message "initial file 1" #clone subrepo we want to add hg clone http://rc.local/subrepo ## use path like url to existing repo in Kallithea echo "subrepo = http://rc.local/subrepo" > .hgsub hg add .hgsub hg ci --message "added remote subrepo" In file list of repo1 you will see a connected subrepo at revision it was during cloning. Clicking in subrepos link should send you to proper repository in Kallithea cloning repo1 will also clone attached subrepository. Next we can edit the subrepo data, and push back to Kallithea. This will update both of repositories. see http://mercurial.aragost.com/kick-start/en/subrepositories/ for more information about subrepositories