1. 04 Nov, 2014 1 commit
  2. 20 Feb, 2014 1 commit
  3. 12 Nov, 2013 1 commit
  4. 01 Feb, 2013 1 commit
  5. 24 Jan, 2013 1 commit
    • John Keeping's avatar
      git-cvsimport.txt: cvsps-2 is deprecated · 1187ec99
      John Keeping authored
      git-cvsimport relies on version 2 of cvsps and does not work with the
      new version 3.  Since cvsps 3.x does not currently work as well as
      version 2 for incremental import, document this fact.
      Specifically, there is no way to make new git-cvsimport that supports
      cvsps 3.x and have a seamless transition for existing users since cvsps
      3.x needs a time from which to continue importing and git-cvsimport does
      not save the time of the last import or import into a specific namespace
      so there is no safe way to calculate the time of the last import.
      Signed-off-by: John Keeping's avatarJohn Keeping <[email protected]>
      Signed-off-by: default avatarJunio C Hamano <[email protected]>
  6. 28 Dec, 2012 1 commit
  7. 17 Oct, 2012 1 commit
  8. 11 Mar, 2011 1 commit
    • Jeff King's avatar
      doc: drop author/documentation sections from most pages · 48bb914e
      Jeff King authored
      The point of these sections is generally to:
        1. Give credit where it is due.
        2. Give the reader an idea of where to ask questions or
           file bug reports.
      But they don't do a good job of either case. For (1), they
      are out of date and incomplete. A much more accurate answer
      can be gotten through shortlog or blame.  For (2), the
      correct contact point is generally [email protected], and even if you
      wanted to cc the contact point, the out-of-date and
      incomplete fields mean you're likely sending to somebody
      So let's drop the fields entirely from all manpages except
      git(1) itself. We already point people to the mailing list
      for bug reports there, and we can update the Authors section
      to give credit to the major contributors and point to
      shortlog and blame for more information.
      Each page has a "This is part of git" footer, so people can
      follow that to the main git manpage.
  9. 20 Jul, 2010 1 commit
  10. 06 Feb, 2010 1 commit
  11. 10 Jan, 2010 1 commit
    • Thomas Rast's avatar
      Documentation: spell 'git cmd' without dash throughout · 0b444cdb
      Thomas Rast authored
      The documentation was quite inconsistent when spelling 'git cmd' if it
      only refers to the program, not to some specific invocation syntax:
      both 'git-cmd' and 'git cmd' spellings exist.
      The current trend goes towards dashless forms, and there is precedent
      in 647ac702 (git-svn.txt: stop using dash-form of commands.,
      2009-07-07) to actively eliminate the dashed variants.
      Replace 'git-cmd' with 'git cmd' throughout, except where git-shell,
      git-cvsserver, git-upload-pack, git-receive-pack, and
      git-upload-archive are concerned, because those really live in the
  12. 20 Apr, 2009 1 commit
  13. 01 Apr, 2009 1 commit
  14. 26 Mar, 2009 1 commit
  15. 25 Mar, 2009 1 commit
  16. 06 Jul, 2008 1 commit
  17. 05 Jul, 2008 1 commit
  18. 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]>
  19. 06 Jun, 2008 1 commit
  20. 01 Mar, 2008 1 commit
  21. 13 Feb, 2008 1 commit
  22. 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]>
  23. 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]>
  24. 06 Jun, 2007 1 commit
  25. 06 Apr, 2007 4 commits
  26. 28 Feb, 2007 1 commit
  27. 18 Jan, 2007 1 commit
  28. 17 Jan, 2007 1 commit
  29. 08 Jan, 2007 2 commits
  30. 02 Aug, 2006 1 commit
  31. 20 Mar, 2006 1 commit
    • Francis Daly's avatar
      Fix multi-paragraph list items in OPTIONS section · 3070b603
      Francis Daly authored
      This patch makes the html docs right, makes the asciidoc docs a bit odd
      but consistent with what is there already, and makes the manpages look
      OK using docbook-xsl 1.68, but miss a paragraph separator when using 1.69.
      For the manpages, current is like
             -A <author_file>
                    Read a file with lines on the form
                    username = User's Full Name <[email protected]>
                    and use "User's Full Name <[email protected]>" as the GIT
      With this patch, docbook-xsl v1.68 looks like
             -A <author_file>
                    Read a file with lines on the form
                            username = User's Full Name <[email protected]>
                    and use "User's Full Name <[email protected]>" as the GIT author and
      while docbook-xsl v1.69 becomes
             -A <author_file>
                    Read a file with lines on the form
                              username = User's Full Name <[email protected]>
                    and use "User's Full Name <[email protected]>" as the GIT author and
      The extra indentation is to keep the v1.69 manpage looking sane.
  32. 08 Mar, 2006 1 commit
  33. 16 Jan, 2006 1 commit
  34. 06 Jan, 2006 1 commit
  35. 08 Dec, 2005 1 commit