git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Vincent Legoll" <vincent.legoll@gmail.com>
To: spearce@spearce.org, git@vger.kernel.org
Subject: Re: [PATCH][EGIT] README typo fixes
Date: Fri, 15 Feb 2008 00:19:12 +0100	[thread overview]
Message-ID: <4727185d0802141519q39cc8f89yc9da993244e71cab@mail.gmail.com> (raw)
In-Reply-To: <4727185d0802141447j4b34958eg5dea5daf52346345@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 65 bytes --]

Looks like I forgot the patch, here it is...

-- 
Vincent Legoll

[-- Attachment #2: 0001-Fix-typos-whitespace-etc.patch --]
[-- Type: application/octet-stream, Size: 4273 bytes --]

From 9cc8b20f75eb10cb497d6dfbb015913e09317e26 Mon Sep 17 00:00:00 2001
From: Vincent Legoll <vincent.legoll@gmail.com>
Date: Thu, 14 Feb 2008 23:15:26 +0100
Subject: [PATCH] - Fix typos, whitespace, etc...

---
 README |   25 +++++++++++++------------
 1 files changed, 13 insertions(+), 12 deletions(-)

diff --git a/README b/README
index 7f6d16a..5ef84be 100644
--- a/README
+++ b/README
@@ -91,7 +91,7 @@ three for packaging.
   in future versions.
 
 - Newer version of EGit/JGit may implement new functionality, remove
-  existing functios and change others without other notice than what
+  existing functions and change others without other notice than what
   is written in the commit log and source files themselves.
 
 
@@ -124,8 +124,8 @@ three for packaging.
 
     * Checkout in dirty working directory if trivial.
 
-    * Walk a the history from a given set of commits looking for commits
-      introducing changed in a path.
+    * Walk the history from a given set of commits looking for commits
+      introducing changes in files under a specified path.
 
   org.spearce.egit.core/
 
@@ -154,7 +154,7 @@ three for packaging.
       for existing repository directories.
 
     * Team actions: track (add), untrack (remove), disconnect, show
-      history, compare version, show history.
+      history, compare version.
 
     * Resource decorator shows file/directory state in the package
       explorer and other views.
@@ -166,7 +166,7 @@ three for packaging.
 
             == Missing Features                ==
 
-There are a lot of missig features. You need the real Git for this.
+There are a lot of missing features. You need the real Git for this.
 For some operations it may just be the preferred solution also. There
 are not just a command line, there is e.g. git-gui that makes committing
 partial files simple.
@@ -176,15 +176,15 @@ partial files simple.
 
 - Merging. 
 
-- Repacking from withine the plugin.
+- Repacking from within the plugin.
 
 - Generate a GIT format patch.
 
 - Apply a GIT format patch.
 
-- Documentation.  :-)
+- Documentation. :-)
 
-- Windows support is new and very little tested. Do not blame us if
+- Windows support is new and very ligthly tested. Do not blame us if
   it blows, but tell us about it and what you did. Double check
   everything.
 
@@ -195,7 +195,7 @@ partial files simple.
 - submodule support
   Submodules are not supported or even recognized.
 
-- The Eclipse plygin cannot handle files outside any Eclipse project. You
+- The Eclipse plugin cannot handle files outside any Eclipse project. You
   need commit changes to such files outside of Eclipse.
 
 - Speed in some areas
@@ -208,7 +208,7 @@ partial files simple.
   the plugin have been optimized but not all and not conclusively. In general
   however Java almost always needs more memory than an application written in 
   e.g. C. In particular there is an overhead from the rather large standard
-  libraries that a normal Java installations comes with. See the ACM report:
+  libraries that a normal Java installation comes with. See the ACM report:
 
 	Prechelt, L. 1999. Technical opinion: comparing Java vs. C/C++
         efficiency differences to interpersonal differences. Commun. ACM 42, 
@@ -222,7 +222,7 @@ partial files simple.
   The conclusion from having about 30 programmers write a program to the same
   specification using their own choice of language (from C,C++ and Java) is
   that the skills of the programmer is what determines the performance of the
-  code rather than choice  of programming language.
+  code rather than choice of programming language.
 
   JGit is much slower (measured up to eight times for some random cases), but
   then the real Git is ridicilously fast.
@@ -230,7 +230,7 @@ partial files simple.
 
             == Support                         ==
 
-  Post question, comments patches to the git@vger.kernel.org mailing list.
+  Post question, comments or patches to the git@vger.kernel.org mailing list.
 
 
             == Contributing                    ==
@@ -247,3 +247,4 @@ C based implementation can be obtained from the GIT websites:
   http://git.or.cz/
   http://www.kernel.org/pub/software/scm/git/
   http://www.kernel.org/pub/software/scm/git/docs/
+
-- 
1.5.4


  parent reply	other threads:[~2008-02-14 23:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14 22:47 [PATCH][EGIT] README typo fixes Vincent Legoll
2008-02-14 23:18 ` Johannes Schindelin
2008-02-14 23:19 ` Vincent Legoll [this message]
2008-02-16 22:33   ` Robin Rosenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4727185d0802141519q39cc8f89yc9da993244e71cab@mail.gmail.com \
    --to=vincent.legoll@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).