git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Max Nanasy <max.nanasy@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Max Nanasy <max.nanasy@gmail.com>
Subject: [PATCH v2] diff.c: diff.renamelimit => diff.renameLimit in message
Date: Thu, 21 Mar 2013 15:14:38 -0700	[thread overview]
Message-ID: <1363904078-98433-1-git-send-email-max.nanasy@gmail.com> (raw)
In-Reply-To: <7va9pwa3h9.fsf@alter.siamese.dyndns.org>

In the warning message printed when rename or unmodified copy
detection was skipped due to too many files, change "diff.renamelimit"
to "diff.renameLimit", in order to make it consistent with git
documentation, which consistently uses "diff.renameLimit".

Signed-off-by: Max Nanasy <max.nanasy@gmail.com>
---

Junio C Hamano <gitster <at> pobox.com> writes:

> 
> The patch is severely whitespace damaged.  If you plan to keep
> contributing to Git, I'd like to make sure that your mail toolchain
> is sane, so that we do not have to keep hand-adjusting patches
> submitted by you before applying.
> 

I composed the first patch through the GMail web interface, which converted
tabs to spaces.  I'm retrying this one through git send-email.

 diff.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/diff.c b/diff.c
index 156fec4..052974e 100644
--- a/diff.c
+++ b/diff.c
@@ -4662,7 +4662,7 @@ int diff_result_code(struct diff_options *opt, int status)
 {
 	int result = 0;
 
-	diff_warn_rename_limit("diff.renamelimit",
+	diff_warn_rename_limit("diff.renameLimit",
 			       opt->needed_rename_limit,
 			       opt->degraded_cc_to_c);
 	if (!DIFF_OPT_TST(opt, EXIT_WITH_STATUS) &&
-- 
1.8.1.3

      reply	other threads:[~2013-03-21 22:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 19:53 [PATCH] diff.c: diff.renamelimit => diff.renameLimit in message Max Nanasy
2013-03-21 20:43 ` Junio C Hamano
2013-03-21 22:14   ` Max Nanasy [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=1363904078-98433-1-git-send-email-max.nanasy@gmail.com \
    --to=max.nanasy@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).