1. 06 Aug, 2013 3 commits
    • Eric Sunshine's avatar
      range-set: publish API for re-use by git-blame -L · c0babbe6
      Eric Sunshine authored
      git-blame is slated to accept multiple -L ranges.  git-log already
      accepts multiple -L's but its implementation of range-set, which
      organizes and normalizes -L ranges, is private.  Publish the small
      subset of range-set API which is needed for git-blame multiple -L
      support.
      Signed-off-by: Eric Sunshine's avatarEric Sunshine <[email protected]>
      Signed-off-by: default avatarJunio C Hamano <[email protected]>
      c0babbe6
    • Eric Sunshine's avatar
      line-range-format.txt: clarify -L:regex usage form · 0ddd4719
      Eric Sunshine authored
      blame/log documentation describes -L option as:
      
        -L<start>,<end>
        -L:<regex>
      
        <start> and <end> can take one of these forms:
      
          * number
          * /regex/
          * +offset or -offset
          * :regex
      
      which is incorrect and confusing since :regex is not one of the valid
      forms of <start> or <end>; in fact, it must be -L's lone argument.
      
      Clarify by discussing :<regex> at the same indentation level as "<start>
      and <end>...":
      
        -L<start>,<end>
        -L:<regex>
      
        <start> and <end> can take one of these forms:
      
          * number
          * /regex/
          * +offset or -offset
      
        If :<regex> is given in place of <start> and <end> ...
      Signed-off-by: Eric Sunshine's avatarEric Sunshine <[email protected]>
      Signed-off-by: default avatarJunio C Hamano <[email protected]>
      0ddd4719
    • Eric Sunshine's avatar
      git-log.txt: place each -L option variation on its own line · 1e159833
      Eric Sunshine authored
      Standard practice in Git documentation is for each variation of an
      option (such as: -p / --porcelain) to be placed on its own line in the
      OPTIONS table. The -L option does not follow suit. It cuddles "-L
      <start>,<end>:<file>" and "-L :<regex>:<file>", separated by a comma.
      This is inconsistent and potentially confusing since the comma
      separating them is typeset the same as the comma in "<start>,<end>". Fix
      this by placing each variation on its own line.
      Signed-off-by: Eric Sunshine's avatarEric Sunshine <[email protected]>
      Signed-off-by: default avatarJunio C Hamano <[email protected]>
      1e159833
  2. 05 Aug, 2013 21 commits
  3. 03 Aug, 2013 1 commit
  4. 02 Aug, 2013 3 commits
    • Junio C Hamano's avatar
      Merge branch 'rj/cygwin-clarify-use-of-cheating-lstat' · d6cbf2fa
      Junio C Hamano authored
      Cygwin port added a "not quite correct but a lot faster and good
      enough for many lstat() calls that are only used to see if the
      working tree entity matches the index entry" lstat() emulation some
      time ago, and it started biting us in places.  This removes it and
      uses the standard lstat() that comes with Cygwin.
      
      Recent topic that uses lstat on packed-refs file is broken when
      this cheating lstat is used, and this is a simplest fix that is
      also the cleanest direction to go in the long run.
      
      * rj/cygwin-clarify-use-of-cheating-lstat:
        cygwin: Remove the Win32 l/stat() implementation
      d6cbf2fa
    • Junio C Hamano's avatar
      Merge branch 'jk/cat-file-batch-optim' · c7eb614c
      Junio C Hamano authored
      * jk/cat-file-batch-optim:
        Revert "cat-file: split --batch input lines on whitespace"
      c7eb614c
    • Junio C Hamano's avatar
      Revert "cat-file: split --batch input lines on whitespace" · 062aeee8
      Junio C Hamano authored
      This reverts commit c334b87b; the
      update assumed that people only used the command to read from
      "rev-list --objects" output, whose lines begin with a 40-hex object
      name followed by a whitespace, but it turns out that scripts feed
      random extended SHA-1 expressions (e.g. "HEAD:$pathname") in which
      a whitespace has to be kept.
      062aeee8
  5. 01 Aug, 2013 7 commits
  6. 31 Jul, 2013 5 commits