From: Marc Branchaud <marcnarc@xiplink.com>
To: Li Peng <lip@dtdream.com>, git@vger.kernel.org
Cc: mmogilvi_git@miniinfo.net
Subject: Re: [PATCH] git-cvsserver: fix duplicate words
Date: Fri, 6 May 2016 09:59:55 -0400 [thread overview]
Message-ID: <572CA35B.80807@xiplink.com> (raw)
In-Reply-To: <1462536570-17199-1-git-send-email-lip@dtdream.com>
On 2016-05-06 08:09 AM, Li Peng wrote:
> Fix duplicate words in comments.
>
> Signed-off-by: Li Peng <lip@dtdream.com>
> ---
> git-cvsserver.perl | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/git-cvsserver.perl b/git-cvsserver.perl
> index 02c0445..392e59e 100755
> --- a/git-cvsserver.perl
> +++ b/git-cvsserver.perl
> @@ -1156,7 +1156,7 @@ sub prepDirForOutput
> # FUTURE: This would more accurately emulate CVS by sending
> # another copy of sticky after processing the files in that
> # directory. Or intermediate: perhaps send all sticky's for
> - # $seendirs after after processing all files.
> + # $seendirs after processing all files.
> }
>
> # update \n
> @@ -2824,7 +2824,7 @@ sub statecleanup
> }
>
> # Return working directory CVS revision "1.X" out
> -# of the the working directory "entries" state, for the given filename.
> +# of the working directory "entries" state, for the given filename.
> # This is prefixed with a dash if the file is scheduled for removal
> # when it is committed.
> sub revparse
> @@ -2935,7 +2935,7 @@ sub filecleanup
> return $filename;
> }
>
> -# Remove prependdir from the path, so that is is relative to the directory
> +# Remove prependdir from the path, so that is relative to the directory
This one is a typo -- it should be "it is".
Did you write a script to find these? :)
(Also, I agree with Jeff that putting all of these changes into one
patch would have been fine.)
M.
prev parent reply other threads:[~2016-05-06 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 12:09 [PATCH] git-cvsserver: fix duplicate words Li Peng
2016-05-06 13:59 ` Marc Branchaud [this message]
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=572CA35B.80807@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=git@vger.kernel.org \
--cc=lip@dtdream.com \
--cc=mmogilvi_git@miniinfo.net \
/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).