1. 28 May, 2014 1 commit
  2. 21 May, 2014 1 commit
  3. 31 Mar, 2014 1 commit
  4. 05 Feb, 2014 1 commit
  5. 06 Jan, 2014 1 commit
  6. 06 Sep, 2013 1 commit
  7. 27 Aug, 2013 11 commits
  8. 22 Jul, 2013 1 commit
  9. 27 Jun, 2013 1 commit
  10. 23 Jun, 2013 3 commits
  11. 18 Jun, 2013 1 commit
  12. 25 Feb, 2013 1 commit
    • W. Trevor King's avatar
      user-manual: Standardize backtick quoting · 1249d8ad
      W. Trevor King authored
      I tried to always use backticks for:
      * Paths and filenames (e.g. `.git/config`)
      * Compound refs (e.g. `origin/HEAD`)
      * Git commands (e.g. `git log`)
      * Command arguments (e.g. `--pretty`)
      * URLs (e.g. `git://`), as a subset of command arguments
      * Special characters (e.g. `+` in diffs).
      * Config options (e.g. `branch.<name>.remote`)
      
      Branch and tag names are sometimes set off with double quotes,
      sometimes set off with backticks, and sometimes left bare.  I tried to
      judge when the intention was introducing new terms or conventions
      (double quotes), to reference a recently used command argument
      (backticks), or to reference the abstract branch/commit (left bare).
      Obviously these are not particularly crisp definitions, so my
      decisions are fairly arbitrary ;).  When a reference had already been
      introduced, I changed further double-quoted instances to backticked
      instances.
      
      When new backticks increased the length of a line beyond others in
      that block, I re-wrapped blocks to 72 columns.
      Signed-off-by: W. Trevor King's avatarW. Trevor King <[email protected]>
      Signed-off-by: default avatarJunio C Hamano <[email protected]>
      1249d8ad
  13. 24 Feb, 2013 1 commit
  14. 19 Feb, 2013 3 commits
  15. 18 Feb, 2013 6 commits
  16. 14 Feb, 2013 1 commit
  17. 11 Feb, 2013 3 commits
  18. 10 Feb, 2013 1 commit
  19. 01 Feb, 2013 1 commit