From: Felipe Contreras <felipe.contreras@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Duy Nguyen <pclouds@gmail.com>
Subject: Re: [PATCH v7] Add new git-related helper to contrib
Date: Thu, 30 May 2013 06:31:20 -0500 [thread overview]
Message-ID: <CAMP44s25vX1p1Np7yqc9_AqVBme+MCTY88hjhfWdL6KZkxgs7Q@mail.gmail.com> (raw)
In-Reply-To: <CALkWK0=ZbOy6sXOvnTNAqz_UBsUymY1CR_WczT-O3Q+18HJjzQ@mail.gmail.com>
On Thu, May 30, 2013 at 4:01 AM, Ramkumar Ramachandra
<artagnon@gmail.com> wrote:
> Let's do one more review.
>
> Felipe Contreras wrote:
>> diff --git a/contrib/related/git-related b/contrib/related/git-related
>> new file mode 100755
>> index 0000000..1b9b1e7
>> --- /dev/null
>> +++ b/contrib/related/git-related
>> @@ -0,0 +1,120 @@
>> +#!/usr/bin/env ruby
>> +
>> +# This script finds people that might be interested in a patch
>> +# usage: git related <file>
>> +
>> +$since = '5-years-ago'
>> +$min_percent = 10
>> +
>> +class Commit
>> +
>> + attr_reader :persons
>
> Unless you plan to introduce many more fields (I haven't looked at the
> later patches), you might as well implement an #each, like in Commits.
commit.each doesn't make sense; each what?
We could do 'commit.each_person', but why is that so better than
commit.persons.each? It's not.
>> + data.each_line do |line|
>> + if not msg
>> + case line
>> + when /^author ([^<>]+) <(\S+)> (.+)$/
>> + @persons << '%s <%s>' % [$1, $2]
>
> Why capture the third group when $3 is unused?
Completeness.
>> + when /^$/
>> + msg = true
>> + end
>> + else
>> + if line =~ /^(Signed-off|Reviewed|Acked)-by: ([^<>]+) <(\S+?)>$/
>> + @persons << '%s <%s>' % [$2, $3]
>
> Why capture the first group when $1 is unused?
You want to complicate the regex even more with:
/^(?:Signed-off|Reviewed|Acked)-by: ([^<>]+) <(\S+?)>$/
For what purpose?
>> + end
>> + end
>> + end
>> + @persons.uniq!
>> + end
>> +
>> +end
>> +
>> +class Commits
>> +
>> + def initialize
>> + @items = {}
>> + end
>> +
>> + def size
>> + @items.size
>> + end
>> +
>> + def each(&block)
>> + @items.each(&block)
>> + end
>> +
>> + def import
>> + return if @items.empty?
>> + File.popen(%w[git cat-file --batch], 'r+') do |p|
>
> Don't you need rb+ to suppress the CRLF nonsense on Windows?
Who knows.
>> + p.write(@items.keys.join("\n"))
>
> As you might have realized, the parentheses are optional everywhere
> (except when it is required for disambiguation). I'm merely pointing
> it out here, because this line looks especially ugly.
I suspect most Git developers would prefer the traditional function call style.
>> + p.close_write
>> + p.each do |line|
>> + if line =~ /^(\h{40}) commit (\d+)/
>> + id, len = $1, $2
>
> id, len = $1, Integer $2. And drop the .to_i on the next line.
This is way is better.
>> + data = p.read($2.to_i)
>> + @items[id].parse(data)
>> + end
>> + end
>> + end
>> + end
>> +
>> + def get_blame(source, start, len, from)
>> + return if len == 0
>> + len ||= 1
>
> I asked you to use 'len =1 if not len' for clarity, but you didn't like it.
git grep "||=" disagrees.
>> + File.popen(['git', 'blame', '--incremental', '-C', '-C',
>> + '-L', '%u,+%u' % [start, len],
>> + '--since', $since, from + '^',
>> + '--', source]) do |p|
>> + p.each do |line|
>> + if line =~ /^\h{40}/
>> + id = $&
>> + @items[id] = Commit.new(id)
>> + end
>> + end
>> + end
>> + end
>> +
>> + def from_patch(file)
>> + from = source = nil
>> + File.open(file) do |f|
>> + f.each do |line|
>
> File.readlines(file).each do |line|.
That's less efficient.
>> + when /^---\s+(\S+)/
>> + source = $1 != '/dev/null' ? $1[2..-1] : nil
>> + when /^@@ -(\d+)(?:,(\d+))?/
>> + get_blame(source, $1, $2, from) if source and from
>
> Useless capture. When is len ($2) going to be nil?
Junio already went over it, see the diff format.
What's your objective? Block this patch from ever going in?
Not a single one of these comments makes a difference at all, all of
them can wait until after the patch is merged, many of them are a
matter of preferences, and some of them have already been addressed as
precisely that: disagreements in style.
--
Felipe Contreras
next prev parent reply other threads:[~2013-05-30 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 3:32 [PATCH v7] Add new git-related helper to contrib Felipe Contreras
2013-05-30 9:01 ` Ramkumar Ramachandra
2013-05-30 11:31 ` Felipe Contreras [this message]
2013-05-30 12:08 ` Ramkumar Ramachandra
2013-05-30 12:12 ` Felipe Contreras
2013-05-31 7:49 ` Felipe Contreras
2013-05-31 8:03 ` Ramkumar Ramachandra
2013-05-31 8:14 ` Felipe Contreras
2013-05-31 8:28 ` Ramkumar Ramachandra
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMP44s25vX1p1Np7yqc9_AqVBme+MCTY88hjhfWdL6KZkxgs7Q@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).