git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v9 3/4] contrib: related: add option to parse from committish

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 3, 2013, 19:05 UTC
Message-ID
<7v8v2rdnh0.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1369986380-412-4-git-send-email-felipe.contreras@gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> writes:
Show 36 quoted lines
> For example master..feature-a.
>
> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
> ---
>  contrib/related/git-related | 38 ++++++++++++++++++++++++++++++++++++--
>  1 file changed, 36 insertions(+), 2 deletions(-)
>
> diff --git a/contrib/related/git-related b/contrib/related/git-related
> index 3379982..20eb456 100755
> --- a/contrib/related/git-related
> +++ b/contrib/related/git-related
> @@ -1,10 +1,12 @@
>  #!/usr/bin/env ruby
>  
>  # This script finds people that might be interested in a patch
> -# usage: git related <files>
> +# usage: git related <files | rev-list options>
>  
>  $since = '5-years-ago'
>  $min_percent = 10
> +$files = []
> +$rev_args = []
>  
>  class Commit
>  
> @@ -102,10 +104,42 @@ class Commits
>      end
>    end
>  
> +  def from_rev_args(args)
> +    source = nil
> +    File.popen(%w[git rev-list --reverse] + args) do |p|
> +      p.each do |e|
> +        id = e.chomp
> +        @main_commits[id] = true
> +        File.popen(%w[git show -C --oneline] + [id]) do |p|

Is there a solid design choice behind -C, or is it just what happens to have worked for you in practice? If the former, it may want to be explained somewhere (either in the log or in the code) so that later tweaks will not break it, especially given that the invocation of blame seems to use double-C's.

Show 33 quoted lines
> +          p.each do |e|
> +            case e
> +            when /^---\s+(\S+)/
> +              source = $1 != '/dev/null' ? $1[2..-1] : nil
> +            when /^@@ -(\d+)(?:,(\d+))?/
> +              get_blame(source, $1, $2, id) if source
> +            end
> +          end
> +        end
> +      end
> +    end
> +  end
> +
> +end
> +
> +ARGV.each do |e|
> +  if File.exists?(e)
> +    $files << e
> +  else
> +    $rev_args << e
> +  end
>  end
>  
>  commits = Commits.new
> -commits.from_patches(ARGV)
> +if $files.empty?
> +  commits.from_rev_args($rev_args)
> +else
> +  commits.from_patches($files)
> +end
>  commits.import
>  
>  count_per_person = Hash.new(0)
Previous: Felipe ContrerasNext: Felipe Contreras
Message 5 of 8 in “New git-related helper”
  1. 0/4 New git-related helperFelipe Contreras, May 31, 2013
  2. 1/4 Add new git-related helper to contribFelipe Contreras, May 31, 2013
  3. 2/4 contrib: related: add support for multiple patchesFelipe Contreras, May 31, 2013
  4. 3/4 contrib: related: add option to parse from committishFelipe Contreras, May 31, 2013
  5. Junio C HamanoJun 3, 2013
  6. Felipe ContrerasJun 3, 2013
  7. 4/4 contrib: related: parse committish like format-patchFelipe Contreras, May 31, 2013
  8. Junio C HamanoJun 3, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.