Mercurial > kallithea
view docs/usage/subrepos.rst @ 3781:40d50bb7cf2f beta
emailing: log failing emailing as an error
TODO: The failure should be reported back to the user (or the admins). The
system should not silently not send any emails to the targeted recipients.
Even better: it should inform the user whenever emails was (scheduled to be)
sent - and to whom.
author | Mads Kiilerich <madski@unity3d.com> |
---|---|
date | Wed, 10 Apr 2013 03:00:38 +0200 |
parents | 8b8edfc25856 |
children | e73a69cb98dc |
line wrap: on
line source
.. _subrepos: ============================================= working with RhodeCode and mercurial subrepos ============================================= example usage of Subrepos with RhodeCode:: ## 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 RhodeCode 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 RhodeCode cloning repo1 will also clone attached subrepository. Next we can edit the subrepo data, and push back to RhodeCode. This will update both of repositories. see http://mercurial.aragost.com/kick-start/en/subrepositories/ for more information about subrepositories