From 1110a29d22308e4959b7769b1743d9e2732c9eec Mon Sep 17 00:00:00 2001 From: Ben Lynn Date: Tue, 4 Sep 2007 02:33:05 -0700 Subject: [PATCH] Style changes Minor edits --- book.css | 21 +++++++++++++++++++++ clone.txt | 2 +- grandmaster.txt | 2 +- secrets.txt | 3 +-- 4 files changed, 24 insertions(+), 4 deletions(-) diff --git a/book.css b/book.css index 218c6f2..730302f 100644 --- a/book.css +++ b/book.css @@ -92,3 +92,24 @@ div.toc a:hover { .parameter { font-style: italic; } + +h1, h2 { + padding-top: 0.5em; + padding-bottom: 0.17em; + margin: 0; + font-weight: normal; + color: black; + border-bottom: 1px solid #aaaaaa; +} + +h1 { + font-size: 188%; +} + +div.chapter h2 { + font-size: 188%; +} + +div.section h2 { + font-size: 150%; +} diff --git a/clone.txt b/clone.txt index 7790233..6317ab4 100644 --- a/clone.txt +++ b/clone.txt @@ -69,7 +69,7 @@ A popular misconception is that Git is ill-suited for projects requiring an offi A good first approximation is that anything a centralized version control system can do, Git can do better. While not strictly true, one is less likely to make erroneous comparisons with this rule of thumb. -You might not use most of Git's features in a small project, but there is nothing wrong with this as there is negligible overhead. And who knows, perhaps your project will grow beyond your original expectations. It's like using a Swiss army knife to mostly open bottles. On the day you desperately need a screwdriver you'll be glad you have it with you. +You might not use most of Git's features in a small project, but there is nothing wrong with this as there is negligible overhead. Moreover, your project may grow beyond your original expectations. It's like using a Swiss army knife to mostly open bottles. On the day you desperately need a screwdriver you'll be glad you have it with you. == Forking a Project == diff --git a/grandmaster.txt b/grandmaster.txt index dd8a0bf..b9a1e9f 100644 --- a/grandmaster.txt +++ b/grandmaster.txt @@ -29,7 +29,7 @@ and in the "proj.git" directory, run From your computer, you can push via ssh: - $ git push git+ssh://web.server/proj.git HEAD + $ git push web.server:/path/to/proj.git HEAD and people can get your project via diff --git a/secrets.txt b/secrets.txt index e382f5f..21459de 100644 --- a/secrets.txt +++ b/secrets.txt @@ -33,8 +33,7 @@ Lastly, a ''commit'' contains a message, a few tree IDs and information on how t Now suppose somebody tries to rewrite history and attempts to change the contents of a file in an ancient version. Then the ID of the file will change since it's now a different string of bytes. This changes the ID of any tree object referencing this file, which in turn changes the ID of all commit objects involving this tree. The corruption in the bad respository is exposed when everyone realizes all the commits since the mutilated file have the wrong IDs. -I've ignored details such as file permissions and signatures. See the -[[.][references]] for the full story. But in short, so long as the 20 bytes representing the last commit are safe, it's impossible to tamper with a Git repository. +I've ignored details such as file permissions and signatures. See the [[.][references]] for the full story. But in short, so long as the 20 bytes representing the last commit are safe, it's impossible to tamper with a Git repository. == Git Shortcomings == -- 2.11.4.GIT