Files
@ 805ec49152c9
Branch filter:
Location: kallithea/docs/contributing.rst - annotation
805ec49152c9
1.9 KiB
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.
bb35ad076e2f bb35ad076e2f 17c9393e9645 e73a69cb98dc bb35ad076e2f bb35ad076e2f e73a69cb98dc 8af52e1224ff bb35ad076e2f 8af52e1224ff e73a69cb98dc 010e9532801a b53cef6faf22 b53cef6faf22 b53cef6faf22 e73a69cb98dc 053983a464e4 e73a69cb98dc e73a69cb98dc b53cef6faf22 010e9532801a 053983a464e4 e73a69cb98dc 950110f3f99f 950110f3f99f 950110f3f99f 8b8edfc25856 6fdc3b25bc7c 950110f3f99f b53cef6faf22 b53cef6faf22 b53cef6faf22 950110f3f99f 6fdc3b25bc7c 1b9d6b0a92b3 a9a1560dad79 b53cef6faf22 b53cef6faf22 b53cef6faf22 b53cef6faf22 b53cef6faf22 b53cef6faf22 b53cef6faf22 703d3208424c b53cef6faf22 b53cef6faf22 950110f3f99f 8af52e1224ff 9472a0150bf0 9472a0150bf0 9472a0150bf0 | .. _contributing:
=========================
Contributing to Kallithea
=========================
If you would like to contribute to Kallithea, please contact us, any help is
greatly appreciated!
Could I request that you make your source contributions by first forking the
Kallithea repository on bitbucket_
https://bitbucket.org/conservancy/kallithea and then make your changes to
your forked repository. Please post all fixes into **dev** bookmark since your
change might be already fixed there and i try to merge all fixes from dev into
stable, and not the other way. Finally, when you are finished with your changes,
please send us a pull request.
To run Kallithea in a development version you always need to install the latest
required libs. Simply clone Kallithea and switch to beta branch::
hg clone https://kallithea-scm.org/repos/kallithea
after downloading/pulling Kallithea make sure you run::
python setup.py develop
command to install/verify all required packages, and prepare development
enviroment.
There are two files in the directory production.ini and developement.ini copy
the `development.ini` file as rc.ini (which is excluded from version controll)
and put all your changes like db connection or server port in there.
After finishing your changes make sure all tests passes ok. You can run
the testsuite running ``nosetest`` from the project root, or if you use tox
run tox for python2.6-2.7 with multiple database test. When using `nosetests`
test.ini file is used and by default it uses sqlite for tests, edit this file
to change your testing enviroment.
There's a special set of tests for push/pull operations, you can runn them using::
paster serve test.ini --pid-file=test.pid --daemon
KALLITHEA_WHOOSH_TEST_DISABLE=1 KALLITHEA_NO_TMP_PATH=1 nosetests -x kallithea/tests/other/test_vcs_operations.py
kill -9 $(cat test.pid)
| Thank you for any contributions!
.. _bitbucket: http://bitbucket.org/
|