From: Stefan Sperling <stsp@stsp.name>
To: git@vger.kernel.org
Subject: [PATCH] Small comment fix for git-cvsimport.
Date: Fri, 21 Dec 2007 16:57:26 +0100 [thread overview]
Message-ID: <20071221155726.GD1720@ted.stsp.lan> (raw)
Signed-off-by: Stefan Sperling <stsp@stsp.name>
---
git-cvsimport.perl | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/git-cvsimport.perl b/git-cvsimport.perl
index 92648f4..1fa9a22 100755
--- a/git-cvsimport.perl
+++ b/git-cvsimport.perl
@@ -848,7 +848,7 @@ while (<CVS>) {
}
if (!$opt_a && $starttime - 300 - (defined $opt_z ? $opt_z : 300) <= $date) {
# skip if the commit is too recent
- # that the cvsps default fuzz is 300s, we give ourselves another
+ # given that the cvsps default fuzz is 300s, we give ourselves another
# 300s just in case -- this also prevents skipping commits
# due to server clock drift
print "skip patchset $patchset: $date too recent\n" if $opt_v;
--
1.5.3.2
--
stefan
http://stsp.name PGP Key: 0xF59D25F0
reply other threads:[~2007-12-21 15:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20071221155726.GD1720@ted.stsp.lan \
--to=stsp@stsp.name \
--cc=git@vger.kernel.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).