1. 18 9月, 2015 13 次提交
  2. 25 8月, 2015 2 次提交
    • J
      Merge 'jk/git-path' into kn/for-each-tag · 7b8419f0
      Junio C Hamano 提交于
      * jk/git-path:
        memoize common git-path "constant" files
        get_repo_path: refactor path-allocation
        find_hook: keep our own static buffer
        refs.c: remove_empty_directories can take a strbuf
        refs.c: avoid git_path assignment in lock_ref_sha1_basic
        refs.c: avoid repeated git_path calls in rename_tmp_log
        refs.c: simplify strbufs in reflog setup and writing
        path.c: drop git_path_submodule
        refs.c: remove extra git_path calls from read_loose_refs
        remote.c: drop extraneous local variable from migrate_file
        prefer mkpathdup to mkpath in assignments
        prefer git_pathdup to git_path in some possibly-dangerous cases
        add_to_alternates_file: don't add duplicate entries
        t5700: modernize style
        cache.h: complete set of git_path_submodule helpers
        cache.h: clarify documentation for git_path, et al
      7b8419f0
    • J
      Merge 'kn/for-each-tag-branch' into kn/for-each-tag · a123b19e
      Junio C Hamano 提交于
      * kn/for-each-tag-branch:
        for-each-ref: add '--contains' option
        ref-filter: implement '--contains' option
        parse-options.h: add macros for '--contains' option
        parse-option: rename parse_opt_with_commit()
        for-each-ref: add '--merged' and '--no-merged' options
        ref-filter: implement '--merged' and '--no-merged' options
        ref-filter: add parse_opt_merge_filter()
        for-each-ref: add '--points-at' option
        ref-filter: implement '--points-at' option
        tag: libify parse_opt_points_at()
        t6302: for-each-ref tests for ref-filter APIs
      a123b19e
  3. 11 8月, 2015 16 次提交
    • J
      memoize common git-path "constant" files · f932729c
      Jeff King 提交于
      One of the most common uses of git_path() is to pass a
      constant, like git_path("MERGE_MSG"). This has two
      drawbacks:
      
        1. The return value is a static buffer, and the lifetime
           is dependent on other calls to git_path, etc.
      
        2. There's no compile-time checking of the pathname. This
           is OK for a one-off (after all, we have to spell it
           correctly at least once), but many of these constant
           strings appear throughout the code.
      
      This patch introduces a series of functions to "memoize"
      these strings, which are essentially globals for the
      lifetime of the program. We compute the value once, take
      ownership of the buffer, and return the cached value for
      subsequent calls.  cache.h provides a helper macro for
      defining these functions as one-liners, and defines a few
      common ones for global use.
      
      Using a macro is a little bit gross, but it does nicely
      document the purpose of the functions. If we need to touch
      them all later (e.g., because we learned how to change the
      git_dir variable at runtime, and need to invalidate all of
      the stored values), it will be much easier to have the
      complete list.
      
      Note that the shared-global functions have separate, manual
      declarations. We could do something clever with the macros
      (e.g., expand it to a declaration in some places, and a
      declaration _and_ a definition in path.c). But there aren't
      that many, and it's probably better to stay away from
      too-magical macros.
      
      Likewise, if we abandon the C preprocessor in favor of
      generating these with a script, we could get much fancier.
      E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
      But the small amount of saved typing is probably not worth
      the resulting confusion to readers who want to grep for the
      function's definition.
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      f932729c
    • J
      get_repo_path: refactor path-allocation · 0ea68e42
      Jeff King 提交于
      The get_repo_path function calls mkpath() and then does some
      non-trivial operations on it, like calling
      is_git_directory() and read_gitfile(). These are actually
      OK (they do not use more pathname static buffers
      themselves), but it takes a fair bit of work to verify.
      
      Let's use our own strbuf to store the path, and we can
      simply reuse it for each iteration of the loop (we can even
      avoid rewriting the beginning part, since we are trying a
      series of suffixes).
      
      To make the strbuf cleanup easier, we split out a thin
      wrapper. As a bonus, this wrapper can factor out the
      canonicalization that happens in all of the early-return
      code paths.
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      0ea68e42
    • J
      find_hook: keep our own static buffer · 03f2c773
      Jeff King 提交于
      The find_hook function returns the results of git_path,
      which is a static buffer shared by other path-related calls.
      Returning such a buffer is slightly dangerous, because it
      can be overwritten by seemingly unrelated functions.
      
      Let's at least keep our _own_ static buffer, so you can
      only get in trouble by calling find_hook in quick
      succession, which is less likely to happen and more obvious
      to notice.
      
      While we're at it, let's add some documentation of the
      function's limitations.
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      03f2c773
    • J
      refs.c: remove_empty_directories can take a strbuf · 470e28d4
      Jeff King 提交于
      The first thing we do in this function is copy the input
      into a strbuf. Of the 4 callers, 3 of them already have a
      strbuf we could use. Let's just take the strbuf, and convert
      the remaining caller to use a strbuf, rather than a raw
      git_path. This is safer, anyway, as remove_dir_recursively
      is a non-trivial function that might use the pathname
      buffers itself (this is _probably_ OK, as the likely culprit
      would be calling resolve_gitlink_ref, but we do not pass the
      proper flags to ask it to avoid blowing away gitlinks).
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      470e28d4
    • J
      refs.c: avoid git_path assignment in lock_ref_sha1_basic · 5f8ef5b8
      Jeff King 提交于
      Assigning the result of git_path is a bad pattern, because
      it's not immediately obvious how long you expect the content
      to stay valid (and it may be overwritten by subsequent
      calls). Let's use a function-local strbuf here instead,
      which we know is safe (we just have to remember to free it
      in all code paths).
      
      As a bonus, we get rid of a confusing variable-reuse
      ("ref_file" is used for two distinct purposes).
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      5f8ef5b8
    • J
      refs.c: avoid repeated git_path calls in rename_tmp_log · d6549f36
      Jeff King 提交于
      Because it's not safe to store the static-buffer results of
      git_path for a long time, we end up formatting the same
      filename over and over. We can fix this by using a
      function-local strbuf to store the formatted pathname and
      avoid repeating ourselves.
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      d6549f36
    • J
      refs.c: simplify strbufs in reflog setup and writing · 54b418f6
      Jeff King 提交于
      Commit 1a83c240 (git_snpath(): retire and replace with
      strbuf_git_path(), 2014-11-30) taught log_ref_setup and
      log_ref_write_1 to take a strbuf parameter, rather than a
      bare string. It then makes an alias to the strbuf's "buf"
      field under the original name.
      
      This made the original diff much shorter, but the resulting
      code is more complicated that it needs to be. Since we've
      aliased the pointer, we drop our reference to the strbuf to
      ensure we don't accidentally change it. But if we simply
      drop our alias and use "logfile.buf" directly, we do not
      have to worry about this aliasing. It's a larger diff, but
      the resulting code is simpler.
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      54b418f6
    • J
      path.c: drop git_path_submodule · 07e3070d
      Jeff King 提交于
      There are no callers of the slightly-dangerous static-buffer
      git_path_submodule left. Let's drop it.
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      07e3070d
    • J
      refs.c: remove extra git_path calls from read_loose_refs · f5b2dec1
      Jeff King 提交于
      In iterating over the loose refs in "refs/foo/", we keep a
      running strbuf with "refs/foo/one", "refs/foo/two", etc. But
      we also need to access these files in the filesystem, as
      ".git/refs/foo/one", etc. For this latter purpose, we make a
      series of independent calls to git_path(). These are safe
      (we only use the result to call stat()), but assigning the
      result of git_path is a suspicious pattern that we'd rather
      avoid.
      
      This patch keeps a running buffer with ".git/refs/foo/", and
      we can just append/reset each directory element as we loop.
      This matches how we handle the refnames. It should also be
      more efficient, as we do not keep formatting the same
      ".git/refs/foo" prefix (which can be arbitrarily deep).
      
      Technically we are dropping a call to strbuf_cleanup() on
      each generated filename, but that's OK; it wasn't doing
      anything, as we are putting in single-level names we read
      from the filesystem (so it could not possibly be cleaning up
      cruft like "./" in this instance).
      
      A clever reader may also note that the running refname
      buffer ("refs/foo/") is actually a subset of the filesystem
      path buffer (".git/refs/foo/"). We could get by with one
      buffer, indexing the length of $GIT_DIR when we want the
      refname. However, having tried this, the resulting code
      actually ends up a little more confusing, and the efficiency
      improvement is tiny (and almost certainly dwarfed by the
      system calls we are making).
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      f5b2dec1
    • J
      remote.c: drop extraneous local variable from migrate_file · b21a5d66
      Jeff King 提交于
      It's an anti-pattern to assign the result of git_path to a
      variable, since other calls may reuse our buffer. In this
      case, we feed the result to unlink_or_warn immediately
      afterwards, so it's OK. However, it's nice to avoid
      assignment entirely, which makes it more obvious that
      there's no bug.
      
      We can just pass the result directly to unlink_or_warn,
      which is a known-simple function. As a bonus, the code flow
      is a little more obvious, as we eliminate an extra
      conditional (a reader does not have to wonder any more
      "under which circumstances is 'path' set?").
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      b21a5d66
    • J
      prefer mkpathdup to mkpath in assignments · e3cf2303
      Jeff King 提交于
      As with the previous commit to git_path, assigning the
      result of mkpath is suspicious, since it is not clear
      whether we will still depend on the value after it may have
      been overwritten by subsequent calls. This patch converts
      low-hanging fruit to use mkpathdup instead of mkpath (with
      the downside that we must remember to free the result).
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      e3cf2303
    • J
      prefer git_pathdup to git_path in some possibly-dangerous cases · fcd12db6
      Jeff King 提交于
      Because git_path uses a static buffer that is shared with
      calls to git_path, mkpath, etc, it can be dangerous to
      assign the result to a variable or pass it to a non-trivial
      function. The value may change unexpectedly due to other
      calls.
      
      None of the cases changed here has a known bug, but they're
      worth converting away from git_path because:
      
        1. It's easy to use git_pathdup in these cases.
      
        2. They use constructs (like assignment) that make it
           hard to tell whether they're safe or not.
      
      The extra malloc overhead should be trivial, as an
      allocation should be an order of magnitude cheaper than a
      system call (which we are clearly about to make, since we
      are constructing a filename). The real cost is that we must
      remember to free the result.
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      fcd12db6
    • J
      add_to_alternates_file: don't add duplicate entries · 77b9b1d1
      Jeff King 提交于
      The add_to_alternates_file function blindly uses
      hold_lock_file_for_append to copy the existing contents, and
      then adds the new line to it. This has two minor problems:
      
        1. We might add duplicate entries, which are ugly and
           inefficient.
      
        2. We do not check that the file ends with a newline, in
           which case we would bogusly append to the final line.
           This is quite unlikely in practice, though, as we call
           this function only from git-clone, so presumably we are
           the only writers of the file (and we always add a
           newline).
      
      Instead of using hold_lock_file_for_append, let's copy the
      file line by line, which ensures all records are properly
      terminated. If we see an extra line, we can simply abort the
      update (there is no point in even copying the rest, as we
      know that it would be identical to the original).
      
      As a bonus, we also get rid of some calls to the
      static-buffer mkpath and git_path functions.
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      77b9b1d1
    • J
      t5700: modernize style · bc192300
      Jeff King 提交于
      The early part of this test is rather old, and does not
      follow our usual style guidelines. In particular:
      
        - the tests liberally chdir, and expect out-of-test "cd"
          commands to return them to a sane state
      
        - test commands aren't indented at all
      
        - there are a lot of minor formatting nits, like the
          opening quote of the test block on the wrong line,
          spaces after ">", etc
      
      This patch fixes the style issues, and uses a few helper
      functions, along with subshells and "git -C", to avoid
      changing the cwd of the main script.
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      bc192300
    • J
      cache.h: complete set of git_path_submodule helpers · f5895fd3
      Jeff King 提交于
      The git_path function has "git_pathdup" and
      "strbuf_git_path" variants, but git_submodule_path only
      comes in the dangerous, static-buffer variant. That makes
      refactoring callers to use the safer functions hard (since
      they don't exist).
      
      Since we're already using a strbuf behind the scenes, it's
      easy to expose all three of these interfaces with thin
      wrappers.
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      f5895fd3
    • J
      cache.h: clarify documentation for git_path, et al · 69ddd231
      Jeff King 提交于
      The comment above these functions actually describes
      sha1_file_name, and comes from the very first revision of
      git. Commit 723c31fe (Add "git_path()" and "head_ref()"
      helper functions., 2005-07-05) added git_path, pushing the
      comment away from the function it describes; later commits
      added more functions in this block.
      
      Let's fix the comment to describe these related functions in
      more detail. Let's also make sure to point out their safer
      alternatives (and move those alternatives below, which makes
      more sense when reading the file).
      
      Note that we do not need to move the existing comment to
      sha1_file_name.  Commit d40d535b (sha1_file.c: document a
      bunch of functions defined in the file, 2014-02-21) already
      added a much more descriptive comment to it.
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      69ddd231
  4. 04 8月, 2015 9 次提交
    • J
      Sync with maint · efc8a625
      Junio C Hamano 提交于
      * maint:
        Git 2.4.8
      efc8a625
    • J
      First batch for 2.6 · eb67052b
      Junio C Hamano 提交于
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      eb67052b
    • J
      Merge branch 'es/doc-clean-outdated-tools' · 12b7eda4
      Junio C Hamano 提交于
      * es/doc-clean-outdated-tools:
        Documentation/git-tools: retire manually-maintained list
        Documentation/git-tools: drop references to defunct tools
        Documentation/git-tools: fix item text formatting
        Documentation/git-tools: improve discoverability of Git wiki
        Documentation/git: drop outdated Cogito reference
      12b7eda4
    • J
      Merge branch 'jk/refspec-parse-wildcard' · 8d3981cc
      Junio C Hamano 提交于
      Allow an asterisk as a substring (as opposed to the entirety) of
      a path component for both side of a refspec, e.g.
      "refs/heads/o*:refs/remotes/heads/i*".
      
      * jk/refspec-parse-wildcard:
        refs: loosen restriction on wildcard "*" refspecs
        refs: cleanup comments regarding check_refname_component()
      8d3981cc
    • J
      Merge branch 'da/subtree-date-confusion' · 7a06e63f
      Junio C Hamano 提交于
      "git subtree" (in contrib/) depended on "git log" output to be
      stable, which was a no-no.  Apply a workaround to force a
      particular date format.
      
      * da/subtree-date-confusion:
        contrib/subtree: ignore log.date configuration
      7a06e63f
    • J
      Merge branch 'jx/do-not-crash-receive-pack-wo-head' · 0baebca5
      Junio C Hamano 提交于
      An attempt to delete a ref by pushing into a repositorywhose HEAD
      symbolic reference points at an unborn branch that cannot be
      created due to ref D/F conflict (e.g. refs/heads/a/b exists, HEAD
      points at refs/heads/a) failed.
      
      * jx/do-not-crash-receive-pack-wo-head:
        receive-pack: crash when checking with non-exist HEAD
      0baebca5
    • J
      Merge branch 'db/send-pack-user-signingkey' · 0c547065
      Junio C Hamano 提交于
      The low-level "git send-pack" did not honor 'user.signingkey'
      configuration variable when sending a signed-push.
      
      * db/send-pack-user-signingkey:
        builtin/send-pack.c: respect user.signingkey
      0c547065
    • J
      Merge branch 'zb/userdiff-fountain' · c1240170
      Junio C Hamano 提交于
      New userdiff pattern definition for fountain screenwriting markup
      format.
      
      * zb/userdiff-fountain:
        userdiff: add support for Fountain documents
      c1240170
    • J
      Merge branch 'dt/refs-backend-preamble' · b6d323f1
      Junio C Hamano 提交于
      In preparation for allowing different "backends" to store the refs
      in a way different from the traditional "one ref per file in $GIT_DIR
      or in a $GIT_DIR/packed-refs file" filesystem storage, reduce
      direct filesystem access to ref-like things like CHERRY_PICK_HEAD
      from scripts and programs.
      
      * dt/refs-backend-preamble:
        git-stash: use update-ref --create-reflog instead of creating files
        update-ref and tag: add --create-reflog arg
        refs: add REF_FORCE_CREATE_REFLOG flag
        git-reflog: add exists command
        refs: new public ref function: safe_create_reflog
        refs: break out check for reflog autocreation
        refs.c: add err arguments to reflog functions
      b6d323f1