Skip to content
Snippets Groups Projects
  1. May 17, 2010
  2. May 16, 2010
  3. Jan 08, 2010
  4. May 16, 2010
  5. May 03, 2010
    • Brodie Rao's avatar
      pager: fork and exec pager as parent process · 3c368a1c962d
      Brodie Rao authored
      With the pager as the child process instead of the parent process, the
      termination of the parent Mercurial process can cause the terminal to return
      before the pager exits. Inverting the relationship prevents that issue.
      
      Platforms without fork() will continue to use util.popen().
      3c368a1c962d
  6. May 16, 2010
  7. May 14, 2010
  8. May 04, 2010
    • Gilles Moris's avatar
      merge: avoid to break the dirstate copy status on moved files · 21a7ae13208f
      Gilles Moris authored
      In the case a file is locally tracked as copied in dirstate, and that a merge
      affects this file, this file should not be marked as modified in dirstate, as
      this will break the current copy state.
      Note: only affect working directory merge, not branch merge.
      21a7ae13208f
  9. May 15, 2010
    • Matt Mackall's avatar
      commands: initial audit of exit codes · 6a64813276ed
      Matt Mackall authored
      bisect: clarify None return
      bundle: return 1 on no changes
      clone: return result code
      copy: limit errors to 0/1
      commit: return 1 on no changes
      forget: return 1 on errors
      grep: return 1 if no match found
      remove: return 1 on errors
      resolve: return 1 if something fails to resolve
      rollback: return 1 if no rollback data
      6a64813276ed
  10. May 14, 2010
  11. May 13, 2010
  12. May 12, 2010
  13. May 09, 2010
    • Christian Ebert's avatar
      keyword: support extensions using dorecord, e.g. crecord · 6d0d945f9e52
      Christian Ebert authored
      Provide extendable keyword.recordextensions variable, so other
      extensions beside hgext.record which provide the dorecord function
      can cooperate with hgext.keyword like so (example from crecord):
      
      def extsetup():
          try:
              keyword = extensions.find('keyword')
              keyword.restricted += ' crecord qcrecord'
              try:
                  # use record support in keyword.py if present
                  keyword.recordcommands += ' crecord qcrecord'
                  keyword.recordextensions += ' crecord'
              except AttributeError:
                  pass
          except KeyError:
              pass
      6d0d945f9e52
  14. May 12, 2010
  15. May 10, 2010
  16. May 11, 2010
  17. May 08, 2010
  18. May 11, 2010
  19. Dec 07, 2009
  20. May 03, 2010
    • Greg Ward's avatar
      push: document return values between various repo methods. · 9936ed1d04f4
      Greg Ward authored
      This starts at localrepository.push() and seeps down to
      push_addchangegroup(), push_unbundle(), prepush(), addchangegroup(),
      and leaks out to sshrepository.unbundle(), sshrepository.addchangegroup(),
      and httprepository.unbundle().  Seems to cover everything you ever
      wanted to know about pushing but were afraid to ask.
      9936ed1d04f4
  21. May 01, 2010
  22. May 10, 2010
    • Cédric Duval's avatar
      patchbomb: Reply-To support · f66ca4431eb9
      Cédric Duval authored
      From RFC 5322:
        an optional reply-to field MAY also be included, which contains the field
        name "Reply-To" and a comma-separated list of one or more addresses.
        [...]
        When the "Reply-To:" field is present, it indicates the address(es) to which
        the author of the message suggests that replies be sent.  In the absence of
        the "Reply-To:" field, replies SHOULD by default be sent to the mailbox(es)
        specified in the "From:" field unless otherwise specified by the person
        composing the reply.
      
      Reply-To addresses may be specified either via command line with --reply-to
      or via the 'email' or 'patchbomb' sections of the config file.
      f66ca4431eb9
Loading