From: Thomas Berg <merlin66b@gmail.com>
To: Vitor Antunes <vitor.hda@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-p4: Corrected typo.
Date: Fri, 28 Jan 2011 16:19:33 +0100 [thread overview]
Message-ID: <AANLkTikeB724f_vE6qvu1h1o5JG150mcmaHVBjLkOEWP@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimQhFzEXr=T9F8TJzTeWwKroTt_BG87RtQCLivv@mail.gmail.com>
Hi,
On Fri, Jan 28, 2011 at 12:35 AM, Vitor Antunes <vitor.hda@gmail.com> wrote:
> Hi everyone,
>
> Could anyone comment the 3 patches I sent (being this the last one)?
>
[...]
> On Thu, Nov 25, 2010 at 1:26 AM, Vitor Antunes <vitor.hda@gmail.com> wrote:
>> ---
>> contrib/fast-import/git-p4 | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/contrib/fast-import/git-p4 b/contrib/fast-import/git-p4
>> index 0ea3a44..a466847 100755
>> --- a/contrib/fast-import/git-p4
>> +++ b/contrib/fast-import/git-p4
>> @@ -618,7 +618,7 @@ class P4Submit(Command):
>> if len(detectRenames) > 0:
>> diffOpts = "-M%s" % detectRenames
>> else:
>> - diffOpts = ("", "-M")[self.detectRenames]
>> + diffOpts = ("", "-M")[self.detectRename]
>>
This appears to me to be a bugfix for one of the other patches you
sent, is that right?
If so, maybe you could squash it with the previous patch and re-send
it all to the list?
My other comments for now are:
- you have forgotten to sign off on the patches
- commit messages are normally in imperative rather than past tense
(see Documentation/SubmittingPatches in git)
- In your first patch you wrote:
> The detectRenames option should be set to the desired threshold value.
I'm not sure what threshold value you refer to here, and what values
you can set it to. Am I missing something?
(I'm not very familiar with git rename detection options)
I'm a git-p4 user, so I can test your changes and look a bit more at
your code. Someone verifying it could help getting the patches
applied.
Thanks for improving git-p4!
Cheers,
Thomas Berg
next prev parent reply other threads:[~2011-01-28 15:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 1:38 [PATCH 0/2] git-p4: Rename and copy detection improvements Vitor Antunes
2010-11-19 1:38 ` [PATCH 1/2] git-p4: Don't edit renamed files if not necessary Vitor Antunes
2010-11-19 12:14 ` Vitor Antunes
2010-11-25 1:26 ` [PATCH] git-p4: Corrected typo Vitor Antunes
2011-01-27 23:35 ` Vitor Antunes
2011-01-28 15:19 ` Thomas Berg [this message]
2011-01-29 2:41 ` Vitor Antunes
2011-01-30 23:21 ` Vitor Antunes
2011-01-30 23:34 ` Thomas Berg
2011-01-31 11:25 ` Vitor Antunes
2011-01-31 12:51 ` Thomas Berg
2011-01-31 13:39 ` Vitor Antunes
2011-01-31 15:54 ` Vitor Antunes
2011-02-04 8:59 ` Thomas Berg
2010-11-19 1:38 ` [PATCH 2/2] git-p4: Added copy detection support Vitor Antunes
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=AANLkTikeB724f_vE6qvu1h1o5JG150mcmaHVBjLkOEWP@mail.gmail.com \
--to=merlin66b@gmail.com \
--cc=git@vger.kernel.org \
--cc=vitor.hda@gmail.com \
/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).