From: Jakub Narebski <jnareb@gmail.com>
To: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>,
Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: Petr Baudis <pasky@ucw.cz>,
Christian Couder <chriscool@tuxfamily.org>,
Git List <git@vger.kernel.org>
Subject: Re: [PATCH RFC GSoC] gitweb: Use -M option while using format-patch
Date: Mon, 10 May 2010 18:41:35 +0200 [thread overview]
Message-ID: <201005101841.40011.jnareb@gmail.com> (raw)
In-Reply-To: <4BE82F8D.8060205@gmail.com>
CC-ed Guiseppe Bilotta, author of 'patch' and 'patches' views
(you can find this information using "git blame" or "git log --grep").
On Mon, 10 May 2010, Pavan Kumar Sunkara wrote:
> Add option '-M' to use with format-patch whcih detects
> renames in the commit.
Subject: [PATCH RFC GSoC] gitweb: Use @diff_opts while using format-patch
Make git-format-patch (used by 'patch' and 'patches' views) use the
same rename detection options that git-diff and git-diff-tree (used
by 'commitdiff', 'blobdiff', etc.) use.
Note that I am not sure if it is really a good change, as it might
create patches that (currently) can be applied only with git.
>
> Signed-off-by: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
> ---
>
> gitweb/gitweb.perl | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
> index c356e95..0184de5 100755
> --- a/gitweb/gitweb.perl
> +++ b/gitweb/gitweb.perl
> @@ -6117,7 +6117,7 @@ sub git_commitdiff {
> }
> push @commit_spec, '--root', $hash;
> }
> - open $fd, "-|", git_cmd(), "format-patch", '--encoding=utf8',
> + open $fd, "-|", git_cmd(), "format-patch", '-M', '--encoding=utf8',
+ open $fd, "-|", git_cmd(), "format-patch", @diff_opts, '--encoding=utf8',
or
- open $fd, "-|", git_cmd(), "format-patch", '--encoding=utf8',
- '--stdout', @commit_spec
+ open $fd, "-|", git_cmd(), "format-patch", @diff_opts,
+ '--encoding=utf8', '--stdout', @commit_spec
This patsh is both line-wrapped and whitespace-damaged (tabs replaced
by spacess)
> '--stdout', @commit_spec
> or die_error(500, "Open git-format-patch failed");
> } else {
> --
-- >8 --
Subject: [PATCH RFC GSoC] gitweb: Use @diff_opts while using format-patch
Make git-format-patch (used by 'patch' and 'patches' views) use the
same rename detection options that git-diff and git-diff-tree (used
by 'commitdiff', 'blobdiff', etc.) use.
Signed-off-by: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
Acked-by: Jakub Narebski <jnareb@gmail.com>
---
gitweb/gitweb.perl | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git i/gitweb/gitweb.perl w/gitweb/gitweb.perl
index 225f404..d983ce5 100755
--- i/gitweb/gitweb.perl
+++ w/gitweb/gitweb.perl
@@ -6295,8 +6295,8 @@ sub git_commitdiff {
}
push @commit_spec, '--root', $hash;
}
- open $fd, "-|", git_cmd(), "format-patch", '--encoding=utf8',
- '--stdout', @commit_spec
+ open $fd, "-|", git_cmd(), "format-patch", @diff_opts,
+ '--encoding=utf8', '--stdout', @commit_spec
or die_error(500, "Open git-format-patch failed");
} else {
die_error(400, "Unknown commitdiff format");
next prev parent reply other threads:[~2010-05-10 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 16:08 [PATCH RFC GSoC] gitweb: Use -M option while using format-patch Pavan Kumar Sunkara
2010-05-10 16:41 ` Jakub Narebski [this message]
2010-05-10 16:56 ` Giuseppe Bilotta
2010-05-10 18:11 ` Petr Baudis
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=201005101841.40011.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=giuseppe.bilotta@gmail.com \
--cc=pasky@ucw.cz \
--cc=pavan.sss1991@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.