1. 06 2月, 2014 1 次提交
  2. 07 9月, 2013 1 次提交
  3. 28 8月, 2013 11 次提交
  4. 23 7月, 2013 1 次提交
  5. 28 6月, 2013 1 次提交
  6. 23 6月, 2013 3 次提交
  7. 19 6月, 2013 1 次提交
  8. 26 2月, 2013 1 次提交
    • W
      user-manual: Standardize backtick quoting · 1249d8ad
      W. Trevor King 提交于
      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: NW. Trevor King <wking@tremily.us>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      1249d8ad
  9. 25 2月, 2013 1 次提交
  10. 20 2月, 2013 3 次提交
  11. 19 2月, 2013 1 次提交
  12. 18 2月, 2013 5 次提交
  13. 15 2月, 2013 1 次提交
  14. 11 2月, 2013 4 次提交
  15. 02 2月, 2013 2 次提交
  16. 26 10月, 2012 1 次提交
  17. 14 9月, 2012 1 次提交
  18. 07 8月, 2012 1 次提交