1. 22 May, 2014 1 commit
  2. 09 Aug, 2012 1 commit
  3. 08 Aug, 2012 1 commit
  4. 05 May, 2012 1 commit
    • Johann's avatar
      Be explicit about 'in-place' · 6f3d7ecc
      Johann authored
      On darwin, sed expects an argument for '-i'. Make it empty.
      
      Change-Id: I5dc6cdf667a754b2624f1767eb6e8025df48e308
      6f3d7ecc
  5. 12 Apr, 2012 2 commits
  6. 04 Apr, 2012 1 commit
  7. 29 Mar, 2012 1 commit
    • John Koleszar's avatar
      FTFY: support wordwrapping commit messages · a46ec165
      John Koleszar authored
      It's common for commit messages to be wrapped at odd places. git-gui
      is often to blame. Adds support for automatically fixing up these
      messages if running ftfy --amend, and adds a new option --msg-only for
      fixing only the commit message.
      
      Change-Id: Ia7ea529f8cb7395d34d9b39f1192598e9a1e315b
      a46ec165
  8. 28 Mar, 2012 1 commit
    • John Koleszar's avatar
      FTFY: an automated style corrector · cb265a49
      John Koleszar authored
      This is a utility for applying a limited amount of style correction on
      a change-by-change basis. Rather than a big-bang reformatting, this
      tool attempts to only correct the style in diff hunks that you touch.
      This should make the cosmetic changes small enough that we can mix them
      with functional changes without destroying the diffs, and there's an
      escape hatch for separating the reformatting to a second commit for
      purists and cases where it hurts readability.
      
      At this time, the script requires a clean working tree, so run it after
      you've commited your changes. Run without arguments, the style
      corrections will be applied and left unstaged in your working copy. It
      also supports the --amend option, which will automatically amend your
      HEAD with the corrected style, and --commit, which will create a new
      change dependent on your HEAD that contains only the whitespace changes.
      
      There are a number of ways this could be applied in an automated manner
      if this proves to be useful, either on a project-wide or per-user
      basis. This doesn't buy anything in terms of real code quality, the
      intent here would be to keep formatting nits out of review comments in
      favor of more meaningful ones and help people whose habitual style
      doesn't match the baseline.
      
      Requires astyle[1] 1.24 or newer.
        [1]: http://astyle.sourceforge.net/
      
      Change-Id: I2fb3434de8479655e9811f094029bb90e5d757e1
      cb265a49