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>,
Robin Rosenberg <robin.rosenberg@dewire.com>
Subject: [JGIT PATCH] Fix typos in comments / testcase output
Date: Fri, 12 Dec 2008 10:55:57 +0000 [thread overview]
Message-ID: <1229079357-19167-1-git-send-email-mike@abacus.co.uk> (raw)
Signed-off-by: Mike Ralphson <mike@abacus.co.uk>
---
Is it me, or is the actual maintainer of JGIT/EGIT not actually
mentioned anywhere? Apologies if I've got the to and cc round
the wrong way 8-)
This patch is the product of
find . -name "*.java" -type f -exec aspell --mode=ccpp -c {} \;
I would post my aspell wordlists but they're polluted by other
projects...
Possibly also s/packes to/packs so/ in README?
.../org/spearce/egit/core/GitMoveDeleteHook.java | 2 +-
.../org/spearce/jgit/lib/RepositoryTestCase.java | 2 +-
.../spearce/jgit/revwalk/RevCommitParseTest.java | 2 +-
.../spearce/jgit/transport/BundleWriterTest.java | 2 +-
.../spearce/jgit/transport/FetchConnection.java | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/org.spearce.egit.core/src/org/spearce/egit/core/GitMoveDeleteHook.java b/org.spearce.egit.core/src/org/spearce/egit/core/GitMoveDeleteHook.java
index cc4059c..7faa65a 100644
--- a/org.spearce.egit.core/src/org/spearce/egit/core/GitMoveDeleteHook.java
+++ b/org.spearce.egit.core/src/org/spearce/egit/core/GitMoveDeleteHook.java
@@ -122,7 +122,7 @@ public boolean moveFolder(final IResourceTree tree, final IFolder source,
final IFolder destination, final int updateFlags,
final IProgressMonitor monitor) {
// TODO: Implement this. Should be relatively easy, but consider that
- // Eclipse thinks folders are real thinsgs, while Git does not care.
+ // Eclipse thinks folders are real things, while Git does not care.
return FINISH_FOR_ME;
}
diff --git a/org.spearce.jgit.test/tst/org/spearce/jgit/lib/RepositoryTestCase.java b/org.spearce.jgit.test/tst/org/spearce/jgit/lib/RepositoryTestCase.java
index 8937145..9e48fde 100644
--- a/org.spearce.jgit.test/tst/org/spearce/jgit/lib/RepositoryTestCase.java
+++ b/org.spearce.jgit.test/tst/org/spearce/jgit/lib/RepositoryTestCase.java
@@ -94,7 +94,7 @@ protected void configure() {
/**
* Utility method to delete a directory recursively. It is
- * also used internally. If a file or directory cannote be removed
+ * also used internally. If a file or directory cannot be removed
* it throws an AssertionFailure.
*
* @param dir
diff --git a/org.spearce.jgit.test/tst/org/spearce/jgit/revwalk/RevCommitParseTest.java b/org.spearce.jgit.test/tst/org/spearce/jgit/revwalk/RevCommitParseTest.java
index 805e29e..9b95924 100644
--- a/org.spearce.jgit.test/tst/org/spearce/jgit/revwalk/RevCommitParseTest.java
+++ b/org.spearce.jgit.test/tst/org/spearce/jgit/revwalk/RevCommitParseTest.java
@@ -226,7 +226,7 @@ public void testParse_explicit_bad_encoded() throws Exception {
*
* What happens here is that an encoding us given, but data is not encoded
* that way (and we can detect it), so we try other encodings. Here data could
- * actually be decoded in the stated encoding, but we overide using UTF-8.
+ * actually be decoded in the stated encoding, but we override using UTF-8.
*
* @throws Exception
*/
diff --git a/org.spearce.jgit.test/tst/org/spearce/jgit/transport/BundleWriterTest.java b/org.spearce.jgit.test/tst/org/spearce/jgit/transport/BundleWriterTest.java
index 3cfb8b1..f13d25c 100644
--- a/org.spearce.jgit.test/tst/org/spearce/jgit/transport/BundleWriterTest.java
+++ b/org.spearce.jgit.test/tst/org/spearce/jgit/transport/BundleWriterTest.java
@@ -117,7 +117,7 @@ assertEquals(db.resolve("c").name(), newRepo.resolve("refs/heads/cc")
// Check that we actually needed the first bundle
Repository newRepo2 = createNewEmptyRepo();
fetchResult = fetchFromBundle(newRepo2, bundle);
- fail("We should not be able to fetch from bundle with prerequisistes that are not fulfilled");
+ fail("We should not be able to fetch from bundle with prerequisites that are not fulfilled");
} catch (MissingBundlePrerequisiteException e) {
assertTrue(e.getMessage()
.indexOf(db.resolve("refs/heads/a").name()) >= 0);
diff --git a/org.spearce.jgit/src/org/spearce/jgit/transport/FetchConnection.java b/org.spearce.jgit/src/org/spearce/jgit/transport/FetchConnection.java
index 461ad71..a56ca6c 100644
--- a/org.spearce.jgit/src/org/spearce/jgit/transport/FetchConnection.java
+++ b/org.spearce.jgit/src/org/spearce/jgit/transport/FetchConnection.java
@@ -126,7 +126,7 @@ public void fetch(final ProgressMonitor monitor, final Collection<Ref> want)
* able to supply a fully connected graph to the client (although it may
* only be transferring the parts the client does not yet have). Its faster
* to assume such remote peers are well behaved and send the correct
- * response to the client. In such tranports this method returns false.
+ * response to the client. In such transports this method returns false.
*
* @return true if the last fetch had to perform a connectivity check on the
* client side in order to succeed; false if the last fetch assumed
--
1.6.0.2
next reply other threads:[~2008-12-12 10:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 10:55 Mike Ralphson [this message]
2008-12-12 15:30 ` [JGIT PATCH] Fix typos in comments / testcase output Shawn O. Pearce
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=1229079357-19167-1-git-send-email-mike@abacus.co.uk \
--to=mike@abacus.co.uk \
--cc=git@vger.kernel.org \
--cc=mike.ralphson@gmail.com \
--cc=robin.rosenberg@dewire.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).