Skip to content
Snippets Groups Projects
  1. Apr 17, 2013
  2. Apr 14, 2013
  3. Feb 10, 2013
  4. Dec 09, 2012
  5. Aug 13, 2012
    • Katsunori FUJIWARA's avatar
      doc: add the tool to check section marks in help documents · 07f1ac17
      Katsunori FUJIWARA authored
      This patch adds "doc/check-seclevel.py" which checks below in help
      documents:
      
        - whether unknown or unavailable section marks are used or not
        - whether appropriate section mark is used at sub-sectioning
      
      It should be invoked in "doc" directory.
      
      It checks all help documents of Mercurial (topics, commands,
      extensions), if no file is specified by --file option.
      
      With --file option, it checks contents of the specified file as help
      document, for self testing purpose: -t/-c/-e/-C are used to specify
      what kind of help document contents of the specified file is.
      
      This checking is related to changeset 979b107eaea2.
      07f1ac17
  6. Aug 17, 2012
  7. Jul 25, 2012
    • Katsunori FUJIWARA's avatar
      doc: unify section level between help topics · 979b107e
      Katsunori FUJIWARA authored
      Some help topics use "-" for the top level underlining section mark,
      but "-" is used also for the top level categorization in generated
      documents: "hg.1.html", for example.
      
      So, TOC in such documents contain "sections in each topics", too.
      
      This patch changes underlining section mark in some help topics to
      unify section level in generated documents.
      
      After this patching, levels of each section marks are:
      
        level0
        """"""
          level1
          ======
            level2
            ------
              level3
              ......
                level4
                ######
      
      And use of section markers in each documents are:
      
        - mercurial/help/*.txt can use level1 or more
          (now these use level1 and level2)
      
        - help for core commands can use level2 or more
          (now these use no section marker)
      
        - descriptions of extensions can use level2 or more
          (now hgext/acl uses level2)
      
        - help for commands defined in extension can use level4 or more
          (now "convert" of hgext/convert uses level4)
      
      "Level0" is used as top level categorization only in "doc/hg.1.txt"
      and the intermediate file generated by "doc/gendoc.py", so end users
      don't see it in "hg help" outoput and so on.
      979b107e
  8. May 12, 2012
  9. May 08, 2012
    • Nikolaj Sjujskij's avatar
      build: fix hgrc manpage building with docutils 0.9 · 462dd183
      Nikolaj Sjujskij authored
      Since docutils 0.9, `roman` module has been moved from module directory root
      (i.e. `site-packages/roman.py`) to `docutils.utils` module. Therefore `import
      roman` statement should be wrapped in `try: ... except ImportError: ...` block
      to handle importing correctly.
      462dd183
  10. Apr 30, 2012
    • Martin Geisler's avatar
      doc: update copyright years to 2012 · e49e039a
      Martin Geisler authored
      I sometimes look at a piece of software and if the man page says
      "Copyright 2004", then I'm inclined to think that the project is stale
      or that the authors are lazy. Neither is good publicity for us :-)
      e49e039a
  11. Dec 06, 2011
  12. Oct 20, 2011
  13. Jul 25, 2011
  14. Jun 29, 2011
  15. Jun 16, 2011
  16. May 30, 2011
  17. May 13, 2011
  18. May 09, 2011
  19. May 01, 2011
  20. Apr 17, 2011
  21. Apr 20, 2011
    • Steven Stallion's avatar
      hgweb: support disabling page cache · a1c31c64
      Steven Stallion authored
      By default, hgweb_mod supports caching via the ETag header. This can
      cause some confusion with browsers which cache aggressively. This change
      preserves existing behavior while giving the administrator a knob to
      disable the ETag header.
      a1c31c64
    • Steven Stallion's avatar
      hgweb: support alternate logo url · 616ad3f6
      Steven Stallion authored
      Clicking on the logo image/text in the hgweb interface brings the
      user to the Mercurial project page. The majority of users expect that
      this would bring them to the top level index. I have added a new template
      variable named `logourl' which allows an administrator to change this
      behavior. To stay compatible with existing behavior, `logourl' will
      default to http://mercurial.selenic.com/. This change is very useful in
      large installations where jumping to the index is common.
      616ad3f6
  22. Apr 19, 2011
    • Adrian Buehlmann's avatar
      add: introduce a warning message for non-portable filenames (issue2756) (BC) · 8b252e82
      Adrian Buehlmann authored
      On POSIX platforms, the 'add', 'addremove', 'copy' and 'rename' commands now
      warn if a file has a name that can't be checked out on Windows.
      
      Example:
      
        $ hg add con.xml
        warning: filename contains 'con', which is reserved on Windows: 'con.xml'
        $ hg status
        A con.xml
      
      The file is added despite the warning.
      
      The warning is ON by default. It can be suppressed by setting the config option
      'portablefilenames' in section 'ui' to 'ignore' or 'false':
      
        $ hg --config ui.portablefilenames=ignore add con.xml
        $ hg sta
        A con.xml
      
      If ui.portablefilenames is set to 'abort', then the command is aborted:
      
        $ hg --config ui.portablefilenames=abort add con.xml
        abort: filename contains 'con', which is reserved on Windows: 'con.xml'
      
      On Windows, the ui.portablefilenames config setting is irrelevant and the
      command is always aborted if a problematic filename is found.
      8b252e82
  23. Apr 07, 2011
  24. Mar 24, 2011
    • Patrick Mezard's avatar
      patch: deprecate ui.patch / external patcher feature · 85d74f6b
      Patrick Mezard authored
      Why?
      - Mercurial internal patcher works correctly for regular patches and git
        patches, is much faster at least on Windows and is more extensible.
      - In theory, the external patcher can be used to handle exotic patch formats. I
        do not know any and have not heard about any such use in years.
      - Most patch programs cannot handle git format patches, which makes the API
        caller to decide either to ignore ui.patch by calling patch.internalpatch()
        directly, or take the risk of random failures with valid inputs.
      - One thing a patch program could do Mercurial patcher cannot is applying with
        --reverse. Apparently several shelve like extensions try to use that,
        including passing the "reverse" option to Mercurial patcher, which has been
        removed mid-2009. I never heard anybody complain about that, and would prefer
        reimplementing it anyway.
      
      And from the technical perspective:
      - The external patcher makes everything harder to maintain and implement. EOL
        normalization is not implemented, and I would bet file renames, if supported
        by the patcher, are not correctly recorded in the dirstate.
      - No tests.
      
      How?
      - Remove related documentation
      - Clearly mark patch.externalpatch() as private
      - Remove the debuginstall check. This deprecation request was actually
        triggered by this last point. debuginstall is the only piece of code patching
        without a repository. When migrating to an integrated patch() + updatedir()
        call, this was really a showstopper, all workarounds were either ugly or
        uselessly complicated to implement. If we do not support external patcher
        anymore, the debuginstall check is not useful anymore.
      - Remove patch.externalpatch() after 1.9 release.
      85d74f6b
  25. Mar 08, 2011
  26. Feb 15, 2011
    • Patrick Mezard's avatar
      commit: abort if a subrepo is modified and ui.commitsubrepos=no · d4de90a6
      Patrick Mezard authored
      The default behaviour is to commit subrepositories with uncommitted changes. In
      my experience this is usually undesirable:
      
      - Changes to dependencies are often debugging leftovers
      - Real changes should generally be applied on the source project directly,
        tested then committed. This is not always possible, subversion subrepos may
        include only a small part of the source project, without the tests.
      
      Setting ui.commitsubrepos=no will now abort commits containing such modified
      subrepositories like:
      
        $ hg --config ui.commitsubrepos=no ci -m msg
        abort: uncommitted changes in subrepo sub
      
      I ruled out the hook solution because it does not easily take --include/exclude
      options in account. Also, my main concern is whether this flag could cause
      problems with extensions. If there are legitimate reasons for callers to
      override this behaviour (I could not find any), they might either override at ui
      level, or we could add an argument to localrepo.commit() later.
      
      v2:
      - Renamed ui.commitsubs to ui.commitsubrepos
      - Mention the configuration entry in hg help subrepos
      d4de90a6
  27. Feb 11, 2011
  28. Feb 05, 2011
  29. Feb 01, 2011
Loading