upstream/mercurial-mirror Files · hgext/hooklib/__init__.py

chg: make is possible to call by default an hg binary located next to chg...

chg: make is possible to call by default an hg binary located next to chg When a single version of hg is in use and it's in the PATH, using chg is just a matter of calling chg. But when there are multiple installations of hg+chg around, and hg is referred to with an absolute path, using chg is more annoying because it requires both changing the invocation to hg to use chg, but also setting CHGHG. Currently, we set HGPATH when we build chg to remove the need to set CHGHG in the previous paragraph. But that means chg now hardcodes its installation path, which makes the installation not relocatable. Hence this proposal to make chg find ./hg relative to itself (as opposed to CHGHG=./hg which find hg relative to cwd). This only works on linux as written, but since it's opt-in, it sounds fine. Tested by hand, as I'm not sure how else to test this. Differential Revision: https://phab.mercurial-scm.org/D9006

Joerg Sonnenberger - - Load All Authors

File last commit:

r44897:4cabeea6 default


                r46128:4c8d9b53

default

Download file

             __init__.py
        
                    26 lines
            
             | 1.0 KiB
            
                | text/x-python
            
             |
                PythonLexer
            
             / hgext / hooklib / __init__.py
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      """collection of simple hooks for common tasks (EXPERIMENTAL)

      This extension provides a number of simple hooks to handle issues

      commonly found in repositories with many contributors:

      - email notification when changesets move from draft to public phase

      - email notification when changesets are obsoleted

      - enforcement of draft phase for all incoming changesets

      - enforcement of a no-branch-merge policy

      - enforcement of a no-multiple-heads policy

      The implementation of the hooks is subject to change, e.g. whether to

      implement them as individual hooks or merge them into the notify

      extension as option. The functionality itself is planned to be supported

      long-term.

      """

      from __future__ import absolute_import

      from . import (

          changeset_obsoleted,

          changeset_published,

      )

      # configtable is only picked up from the "top-level" module of the extension,

      # so expand it here to ensure all items are properly loaded

      configtable = {}

      configtable.update(changeset_published.configtable)

      configtable.update(changeset_obsoleted.configtable)

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

				"""collection of simple hooks for common tasks (EXPERIMENTAL)

				This extension provides a number of simple hooks to handle issues
				commonly found in repositories with many contributors:
				- email notification when changesets move from draft to public phase
				- email notification when changesets are obsoleted
				- enforcement of draft phase for all incoming changesets
				- enforcement of a no-branch-merge policy
				- enforcement of a no-multiple-heads policy

				The implementation of the hooks is subject to change, e.g. whether to
				implement them as individual hooks or merge them into the notify
				extension as option. The functionality itself is planned to be supported
				long-term.
				"""
				from __future__ import absolute_import
				from . import (
				changeset_obsoleted,
				changeset_published,
				)

				# configtable is only picked up from the "top-level" module of the extension,
				# so expand it here to ensure all items are properly loaded
				configtable = {}
				configtable.update(changeset_published.configtable)
				configtable.update(changeset_obsoleted.configtable)