Files
@ 805ec49152c9
Branch filter:
Location: kallithea/docs/usage/subrepos.rst - annotation
805ec49152c9
1013 B
text/prs.fallenstein.rst
simplehg: don't quiet Hg output for push
I want to be able to see informational messages from e.g. the Hg Bugzilla
extension.
Here's output without the patch. This is identical to the output produced if
the Bugzilla extension is disabled:
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
remote: Repository size .hg:158.2 kB repo:0 B total:158.2 kB
remote: Last revision is now r324:6c03abbabb46
and with the patch:
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
remote: Repository size .hg:158.2 kB repo:0 B total:158.2 kB
remote: Last revision is now r324:6c03abbabb46
remote: bug 3270 already knows about changeset 6c03abbabb46
The last line indicates that the Bugzilla bug text already contains an entry
for that changeset. It's produced by a call to self.ui.status() in the
extension.
I think the point here is that the deleted code is ensuring that the remote hg
(i.e. the Kallithea hg) always runs with the --quiet flag when receiving a
push. This seems an arbitrary decision to me, and one that removes potentially
useful information from the output. I believe this behaviour is different to
that seen by the user if pushing to hgweb (I've not tried it, but inspected the
hgweb source for setting quiet) and is certainly different to pushing over ssh.
I want to be able to see informational messages from e.g. the Hg Bugzilla
extension.
Here's output without the patch. This is identical to the output produced if
the Bugzilla extension is disabled:
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
remote: Repository size .hg:158.2 kB repo:0 B total:158.2 kB
remote: Last revision is now r324:6c03abbabb46
and with the patch:
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
remote: Repository size .hg:158.2 kB repo:0 B total:158.2 kB
remote: Last revision is now r324:6c03abbabb46
remote: bug 3270 already knows about changeset 6c03abbabb46
The last line indicates that the Bugzilla bug text already contains an entry
for that changeset. It's produced by a call to self.ui.status() in the
extension.
I think the point here is that the deleted code is ensuring that the remote hg
(i.e. the Kallithea hg) always runs with the --quiet flag when receiving a
push. This seems an arbitrary decision to me, and one that removes potentially
useful information from the output. I believe this behaviour is different to
that seen by the user if pushing to hgweb (I've not tried it, but inspected the
hgweb source for setting quiet) and is certainly different to pushing over ssh.
e54ec8211944 e54ec8211944 e54ec8211944 e73a69cb98dc e54ec8211944 e54ec8211944 e73a69cb98dc 8b8edfc25856 e54ec8211944 8b8edfc25856 e54ec8211944 e54ec8211944 8b8edfc25856 e54ec8211944 8b8edfc25856 e54ec8211944 e54ec8211944 e54ec8211944 e73a69cb98dc e54ec8211944 e54ec8211944 e54ec8211944 e54ec8211944 e54ec8211944 8b8edfc25856 e54ec8211944 e54ec8211944 e54ec8211944 e73a69cb98dc e54ec8211944 e54ec8211944 e54ec8211944 e73a69cb98dc e54ec8211944 e54ec8211944 e54ec8211944 8b8edfc25856 | .. _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
|