Re: [PATCH] update README and #include in git.txt

Dear diary, on Sat, May 14, 2005 at 12:29:24AM CEST, I got a letter
where David Greaves [off-list ref] told me that...

quoted

quoted

Index: README
===================================================================

--- 3c79088f1832d78012ccdb63e5da1ab88fcf408e/README  (mode:100644)
+++ e0e578bb02a7d8db1c105fddf5b5168ad0c79088/README  (mode:100644)

@@ -1,9 +1,13 @@
+////////////////////////////////////////////////////////////////
+	GIT - the stupid content tracker


-
-	GIT - the stupid content tracker
+Note that this README is written in asciidoc format and is #include'd
+in the git.txt docs


+The rest of this README is #included in the git.txt file
+////////////////////////////////////////////////////////////////

"git" can mean anything, depending on your mood.

 - random three-letter combination that is pronounceable, and not
   

I'd probably prefer this being much less prominent. Can it be rather at
the bottom of the file?
 

If you mean the header in the ///'s?
yes - but I wanted editors to realise it is asciidoc so kept it at the top.

But it's called README, not EDITME. And I think it's cluttering for the
readers.

quoted

You're reintroducing the "typos" fixed before, apparently.
 

I didn't notice the i.e. vs ie - I'm not that bothered ;)

But there were other typo fixes there and the big reindenting won't show
up any further changes to the text. I don't want to lose them so I'm
concerned now.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor