1. 21 11月, 2017 6 次提交
  2. 15 11月, 2017 24 次提交
  3. 13 11月, 2017 2 次提交
    • J
      link_alt_odb_entries: make empty input a noop · f28e3668
      Jeff King 提交于
      If an empty string is passed to link_alt_odb_entries(), our
      loop finds no entries and we link nothing. But we still do
      some preparatory work to normalize the object directory
      path, even though we'll never look at the result. This
      triggers in basically every git process, since we feed the
      usually-empty ALTERNATE_DB_ENVIRONMENT to the function.
      
      Let's detect early that there's nothing to do and return.
      While we're at it, let's treat NULL the same as an empty
      string as a favor to our callers. That saves
      prepare_alt_odb() from having to cover this case.
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      f28e3668
    • C
      grep: fix NO_LIBPCRE1_JIT to fully disable JIT · 2fff1e19
      Charles Bailey 提交于
      If you have a pcre1 library which is compiled with JIT enabled then
      PCRE_STUDY_JIT_COMPILE will be defined whether or not the
      NO_LIBPCRE1_JIT configuration is set.
      
      This means that we enable JIT functionality when calling pcre_study
      even if NO_LIBPCRE1_JIT has been explicitly set and we just use plain
      pcre_exec later.
      
      Fix this by using own macro (GIT_PCRE_STUDY_JIT_COMPILE) which we set to
      PCRE_STUDY_JIT_COMPILE only if NO_LIBPCRE1_JIT is not set and define to
      0 otherwise, as before.
      Reviewed-by: NÆvar Arnfjörð Bjarmason <avarab@gmail.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      2fff1e19
  4. 09 11月, 2017 4 次提交
  5. 07 11月, 2017 1 次提交
    • B
      wt-status: actually ignore submodules when requested · c6d8ccf3
      Brandon Williams 提交于
      Since ff6f1f56 (submodule-config: lazy-load a repository's .gitmodules
      file, 2017-08-03) rebase interactive fails if there are any submodules
      with unstaged changes which have been configured with a value for
      'submodule.<name>.ignore' in the repository's config.
      
      This is due to how configured values of 'submodule.<name>.ignore' are
      handled in addition to a change in how the submodule config is loaded.
      When the diff machinery hits a submodule (gitlink as well as a
      corresponding entry in the submodule subsystem) it will read the value
      of 'submodule.<name>.ignore' stored in the repository's config and if
      the config is present it will clear the 'IGNORE_SUBMODULES' (which is
      the flag explicitly requested by rebase interactive),
      'IGNORE_UNTRACKED_IN_SUBMODULES', and 'IGNORE_DIRTY_SUBMODULES' diff
      flags and then set one of them based on the configured value.
      
      Historically this wasn't a problem because the submodule subsystem
      wasn't initialized because the .gitmodules file wasn't explicitly loaded
      by the rebase interactive command.  So when the diff machinery hit a
      submodule it would skip over reading any configured values of
      'submodule.<name>.ignore'.
      
      In order to preserve the behavior of submodules being ignored by rebase
      interactive, also set the 'OVERRIDE_SUBMODULE_CONFIG' diff flag when
      submodules are requested to be ignored when checking for unstaged
      changes.
      Reported-by: NOrgad Shaneh <orgads@gmail.com>
      Signed-off-by: NBrandon Williams <bmwill@google.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      c6d8ccf3
  6. 06 11月, 2017 3 次提交