Skip to content
Commits on Jul 28, 2008
  1. @schacon

    reverted the featured git stuff

    schacon committed Jul 28, 2008
  2. @bryceroney

    fixed some indenting issues

    bryceroney committed Jul 28, 2008
  3. @bryceroney

    Featured project functionality via GitHub

    bryceroney committed Jul 28, 2008
    * CSS changes
    * Template changes
    * Added Hpricot to config.
  4. @bryceroney
  5. @bryceroney
  6. @bryceroney

    made script files executable

    bryceroney committed Jul 28, 2008
  7. @bryceroney
Commits on Jul 27, 2008
  1. @schacon
  2. @schacon

    added deploy script

    schacon committed Jul 27, 2008
Commits on Jul 26, 2008
  1. @schacon
  2. @schacon

    added a link to the git wiki

    schacon committed Jul 26, 2008
  3. @schacon
  4. @schacon
  5. @pasky

    Merge commit 'upstream/master'

    pasky committed Jul 26, 2008
  6. @pasky

    documentation.html: More sensible [GitDocumentation] link

    pasky committed Jul 26, 2008
    Spelling out '' does not make much sense to me in this
    context and it's better to keep the link label the same as the
    actual page name.
  7. @pasky

    download.html: Link to both the gitweb and GitHub web interface

    pasky committed Jul 26, 2008
    The gitweb interface is linked because of the graphiclog
    and forking capability, on par with GitHub features; also, simply many
    existing forks of git.git are there already that the readers may find
    There is already a link to gitweb interface in the download box but
    I think the extra redundancy here does no harm, since the reader might
    not think about looking away to a box elsewhere on the page when reading
    about how to access the Git's repository.
  8. @pasky
  9. @pasky

    documentation.html: Highlight one resource per tutorial subsection

    pasky committed Jul 26, 2008
    The most important resource for each subsection of the Tutorial section
    is now in bold, so that the users know what to pick if in doubt.
  10. @pasky

    documentation.html: Shift Git for Designers/CS upwards

    pasky committed Jul 26, 2008
    This will be maybe a bit controversial, but they feel more like an
    introductory, almost tutorial-like material, and I think it makes sense to move
    them up in the reading order for this reason.
  11. @pasky
  12. @pasky

    documentation.html: [Git for Designers] SCM -> version control

    pasky committed Jul 26, 2008
    No knowledge of SCM implies no knowledge of the SCM acronym.
  13. @pasky
  14. @pasky
  15. @pasky

    documentation.html: Cut on the superlatives

    pasky committed Jul 26, 2008
    The superlatives obscure real merit of various resources; of _course_
    we list only great and fantastic stuff. ;-)
  16. @pasky

    documentation.html: Swap "Git for the lazy" and "SVN Crash Course"

    pasky committed Jul 26, 2008
    I think "Git for the lazy" provides the least unique material of the
    series while "SVN Crash Course" can be an equal alternative to the
    official tutorial, with the "Everyday Git" serving as a good
    complementary resource for both.
  17. @pasky

    documentation.html: Documentation/ -> reference manual

    pasky committed Jul 26, 2008
    ...since that's what it really is - now it is more obvious. Also reword
    the rest of the paragraph to accomodate this change.
  18. @pasky

    documentation.html: Move Cheat Sheet above 37signals

    pasky committed Jul 26, 2008
    I think that the Cheat Sheet is more immediately useful and nicer than
    the 37signal resources.
  19. @pasky

    documentation.html: Move "Reference" section to the leftmost column

    pasky committed Jul 26, 2008
    Now, the "Tutorial" section is at the top of the second column, right
    in the center of the page, which I believe is right since this is the
    place the newcomer is probably looking for; it is not good to be pushed
    below by the reference manual.
  20. @schacon
  21. @pasky

    documentation.html: Reorder items in the "Commands" column a bit

    pasky committed Jul 26, 2008
    Now there should be a more natural "workflow progression" reflected
    in the order of listed commands.
  22. @schacon
  23. @pasky
  24. @pasky
  25. @pasky

    index.html: Add missing step in the git init example

    pasky committed Jul 26, 2008
    It makes no sense to commit an empty tree.
  26. @pasky

    index.html: Simpler example git format-patch usage

    pasky committed Jul 26, 2008
    It is unnecessary to --stdout and redirect, git format-patch will create
    the file on its own and show it at the output; thus, this should be fairly
    obvious even for a novice, and it looks better on the web than the
    complicated incanation.
Something went wrong with that request. Please try again.