1. 11 Jan, 2009 2 commits
  2. 07 Jan, 2009 14 commits
  3. 06 Jan, 2009 1 commit
    • Junio C Hamano's avatar
      Merge branch 'maint' · e9b85231
      Junio C Hamano authored
      * maint:
        Be consistent in switch usage for tar
        Use capitalized names where appropriate
        fast-export: print usage when no options specified
  4. 05 Jan, 2009 6 commits
  5. 03 Jan, 2009 4 commits
  6. 02 Jan, 2009 2 commits
    • Junio C Hamano's avatar
      builtin-apply: prevent non-explicit permission changes · 1f7903a3
      Junio C Hamano authored
      A git patch that does not change the executable bit records the mode bits
      on its "index" line.  "git apply" used to interpret this mode exactly the
      same way as it interprets the mode recorded on "new mode" line, as the
      wish by the patch submitter to set the mode to the one recorded on the
      The reason the mode does not agree between the submitter and the receiver
      in the first place is because there is _another_ commit that only appears
      on one side but not the other since their histories diverged, and that
      commit changes the mode.  The patch has "index" line but not "new mode"
      line because its change is about updating the contents without affecting
      the mode.  The application of such a patch is an explicit wish by the
      submitter to only cherry-pick the commit that updates the contents without
      cherry-picking the commit that modifies the mode.  Viewed this way, the
      current behaviour is problematic, even though the command does warn when
      the mode of the path being patched does not match this mode, and a careful
      user could detect this inconsistencies between the patch submitter and the
      patch receiver.
      This changes the semantics of the mode recorded on the "index" line;
      instead of interpreting it as the submitter's wish to set the mode to the
      recorded value, it merely informs what the mode submitter happened to
      have, and the presense of the "index" line is taken as submitter's wish to
      keep whatever the mode is on the receiving end.
      This is based on the patch originally done by Alexander Potashev with a
      minor fix; the tests are mine.
      Signed-off-by: default avatarJunio C Hamano <gitster@pobox.com>
    • Johannes Schindelin's avatar
      git wrapper: Make while loop more reader-friendly · cca17048
      Johannes Schindelin authored
      It is not a good practice to prefer performance over readability in
      something as performance uncritical as finding the trailing slash
      of argv[0].
      So avoid head-scratching by making the loop user-readable, and not
      Signed-off-by: Johannes Schindelin's avatarJohannes Schindelin <johannes.schindelin@gmx.de>
      Signed-off-by: default avatarJunio C Hamano <gitster@pobox.com>
  7. 01 Jan, 2009 3 commits
  8. 29 Dec, 2008 8 commits