From: Mike Ralphson <mike@abacus.co.uk>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org, Mike Ralphson <mike.ralphson@gmail.com>
Subject: [JGIT PATCH] Typos in documentation
Date: Fri, 22 Aug 2008 16:49:46 +0100 [thread overview]
Message-ID: <d03b5675d55bbbd68e3d22b6b28b1f70f7af00b9.1219418949.git.mike@abacus.co.uk> (raw)
---
EGIT_INSTALL | 6 +++---
README | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/EGIT_INSTALL b/EGIT_INSTALL
index 142526a..3a8f249 100644
--- a/EGIT_INSTALL
+++ b/EGIT_INSTALL
@@ -16,7 +16,7 @@ things.
- A reasonably recent version of Git itself installed on your platform to
take care of what the plugin does not yet do or do things that native
- git does better. Some tests have been peformed using both Cygwin and MSYS git.
+ git does better. Some tests have been performed using both Cygwin and MSYS git.
Both have issues that we need both feedback and patches for.
INSTALLATION INSTRUCTIONS
@@ -25,7 +25,7 @@ INSTALLATION INSTRUCTIONS
- Start eclipse
- Make sure a recent JDK 1.5.0_11 or JDK 1.6.x is among your installed JRE's. Which
one is the default should not matter but Java 6 is recommended.
-- Import the egit projects. Make sure there aare no compilation errors
+- Import the egit projects. Make sure there are no compilation errors
- Now you can either export the plugin to a set of jar files to use in an Eclipse
installation or run it from within Eclipse. The latter is for development and
tracking down bugs.
@@ -34,7 +34,7 @@ INSTALLATION INSTRUCTIONS
fragments and choose the Next button. Set Directory to the top of your
installation directory (NOT the plugins directory). Select Finish. After
that restart Eclipse. You can associate a project withe Eclipse using the
- Team>Share meny in the context meny when a project is selected.
+ Team>Share menu in the context menu when a project is selected.
DEBUGGING INSTRUCTIONS
- Select the org.spearce.egit.ui project, and using the context menu select
diff --git a/README b/README
index dd4a910..424f7a3 100644
--- a/README
+++ b/README
@@ -127,7 +127,7 @@ three for packaging.
* Connect/disconnect the provider to a project.
* Search for the repositories associated with a project by
- autodecting the GIT repository directories.
+ autodetecting the GIT repository directories.
* Store which repositories are tied to which containers in the
Eclipse workspace.
--
1.5.6.4
next reply other threads:[~2008-08-22 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 15:49 Mike Ralphson [this message]
2008-08-22 15:49 ` [JGIT PATCH] Typos in error messages etc Mike Ralphson
2008-08-22 15:49 ` [JGIT PATCH] Typos in comments Mike Ralphson
2008-08-22 15:59 ` [JGIT PATCH] Typos in documentation Shawn O. Pearce
2008-08-22 16:00 ` Shawn O. Pearce
2008-08-22 16:08 ` Mike Ralphson
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=d03b5675d55bbbd68e3d22b6b28b1f70f7af00b9.1219418949.git.mike@abacus.co.uk \
--to=mike@abacus.co.uk \
--cc=git@vger.kernel.org \
--cc=mike.ralphson@gmail.com \
--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).