1. 18 Jun, 2009 1 commit
  2. 05 Jul, 2008 1 commit
  3. 02 Jul, 2008 2 commits
    • Jonathan Nieder's avatar
      Documentation formatting and cleanup · 483bc4f0
      Jonathan Nieder authored
      Following what appears to be the predominant style, format
      names of commands and commandlines both as `teletype text`.
      While we're at it, add articles ("a" and "the") in some
      places, italicize the name of the command in the manual page
      synopsis line, and add a comma or two where it seems appropriate.
      Signed-off-by: default avatarJonathan Nieder <[email protected]>
      Signed-off-by: default avatarJunio C Hamano <[email protected]>
    • Jonathan Nieder's avatar
      Documentation: be consistent about "git-" versus "git " · b1889c36
      Jonathan Nieder authored
      Since the git-* commands are not installed in $(bindir), using
      "git-command <parameters>" in examples in the documentation is
      not a good idea. On the other hand, it is nice to be able to
      refer to each command using one hyphenated word. (There is no
      escaping it, anyway: man page names cannot have spaces in them.)
      This patch retains the dash in naming an operation, command,
      program, process, or action. Complete command lines that can
      be entered at a shell (i.e., without options omitted) are
      made to use the dashless form.
      The changes consist only of replacing some spaces with hyphens
      and vice versa. After a "s/ /-/g", the unpatched and patched
      versions are identical.
      Signed-off-by: default avatarJonathan Nieder <[email protected]>
      Signed-off-by: default avatarJunio C Hamano <[email protected]>
  4. 06 Jun, 2008 1 commit
  5. 21 May, 2008 1 commit
  6. 15 May, 2008 1 commit
    • Johannes Schindelin's avatar
      cvsexportcommit: introduce -W for shared working trees (between Git and CVS) · d775734c
      Johannes Schindelin authored
      If you have a CVS checkout, it is easy to import the CVS history by
      calling "git cvsimport".  However, interacting with the CVS repository
      using "git cvsexportcommit" was cumbersome, since that script assumes
      separate working directories for Git and CVS.
      Now, you can call cvsexportcommit with the -W option.  This will
      automatically discover the GIT_DIR, and it will check out the parent
      commit before exporting the commit.
      The intended workflow is this:
      $ CVSROOT=$URL cvs co module
      $ cd module
      $ git cvsimport
      hack, hack, hack, making two commits, cleaning them up using rebase -i.
      $ git cvsexportcommit -W -c -p -u HEAD^
      $ git cvsexportcommit -W -c -p -u HEAD
      Signed-off-by: Johannes Schindelin's avatarJohannes Schindelin <[email protected]>
      Signed-off-by: default avatarJunio C Hamano <[email protected]>
  7. 07 Jan, 2008 1 commit
    • Dan McGee's avatar
      Documentation: rename gitlink macro to linkgit · 5162e697
      Dan McGee authored
      Between AsciiDoc 8.2.2 and 8.2.3, the following change was made to the stock
      Asciidoc configuration:
      @@ -149,7 +153,10 @@
       # Inline macros.
       # Backslash prefix required for escape processing.
       # (?s) re flag for line spanning.
      +# Explicit so they can be nested.
       # Anchor: [[[id]]]. Bibliographic anchor.
       # Anchor: [[id,xreflabel]]
      This default regex now matches explicit values, and unfortunately in this
      case gitlink was being matched by just 'link', causing the wrong inline
      macro template to be applied. By renaming the macro, we can avoid being
      matched by the wrong regex.
      Signed-off-by: Dan McGee's avatarDan McGee <[email protected]>
      Signed-off-by: default avatarJunio C Hamano <[email protected]>
  8. 02 Nov, 2007 1 commit
  9. 30 Oct, 2007 1 commit
  10. 25 Aug, 2007 1 commit
  11. 16 Jun, 2007 1 commit
    • Junio C Hamano's avatar
      Documentation: adjust to AsciiDoc 8 · 4c7100a9
      Junio C Hamano authored
      It turns out that the attribute definition we have had for a
      long time to hide "^" character from AsciiDoc 7 was not honored
      by AsciiDoc 8 even under "-a asciidoc7compatible" mode.  There is
      a similar breakage with the "compatible" mode with + characters.
      The double colon at the end of definition list term needs
      to be attached to the term, without a whitespace.  After this
      minimum fixups, AsciiDoc 8 (I used 8.2.1 on Debian) with
      compatibility mode seems to produce reasonably good results.
      Signed-off-by: default avatarJunio C Hamano <[email protected]>
  12. 07 Jun, 2007 1 commit
    • Junio C Hamano's avatar
      War on whitespace · a6080a0a
      Junio C Hamano authored
      This uses "git-apply --whitespace=strip" to fix whitespace errors that have
      crept in to our source files over time.  There are a few files that need
      to have trailing whitespaces (most notably, test vectors).  The results
      still passes the test, and build result in Documentation/ area is unchanged.
      Signed-off-by: default avatarJunio C Hamano <[email protected]>
  13. 25 May, 2007 1 commit
  14. 07 May, 2007 1 commit
  15. 21 Feb, 2007 1 commit
  16. 05 Feb, 2007 1 commit
  17. 18 Jan, 2007 1 commit
  18. 24 Jul, 2006 1 commit
  19. 09 Jul, 2006 1 commit
  20. 26 Apr, 2006 1 commit
  21. 30 Jan, 2006 1 commit
  22. 06 Jan, 2006 1 commit
  23. 13 Dec, 2005 1 commit
  24. 08 Nov, 2005 1 commit
  25. 07 Nov, 2005 1 commit