Would it make sense to integrate this in git shortlog, which
already
does something similar?
Conceptually, yes, but the end result will be much larger in scope.
I am not sure if shortlog is still a good label for it.
since we are throwing ideas around...
The first place where I
Johannes Sixt j...@kdbg.org writes:
But I think it can be useful outside the context of send-email as
well, and having one independent tool that does one single job well
is a better design. Perhaps it is better to name it less specific
to send-email's cc-cmd option. git people? git whom?
Felipe Contreras wrote:
The code finds the changes of a commit, runs 'git blame' for each chunk
to see which other commits are relevant, and then reports the author and
signers.
Finally, it calculates what percentage of the total relevant commits
each person was involved in, and show only
On Fri, Apr 19, 2013 at 8:26 AM, Ramkumar Ramachandra
artag...@gmail.com wrote:
Felipe Contreras wrote:
The code finds the changes of a commit, runs 'git blame' for each chunk
to see which other commits are relevant, and then reports the author and
signers.
Finally, it calculates what
Felipe Contreras felipe.contre...@gmail.com writes:
The code finds the changes of a commit, runs 'git blame' for each chunk
to see which other commits are relevant, and then reports the author and
signers.
In general, I am not all that interested in adding anything new to
contrib/ as git.git
On Fri, Apr 19, 2013 at 12:08 PM, Junio C Hamano gits...@pobox.com wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
The code finds the changes of a commit, runs 'git blame' for each chunk
to see which other commits are relevant, and then reports the author and
signers.
In general,
Felipe Contreras felipe.contre...@gmail.com writes:
On Fri, Apr 19, 2013 at 12:08 PM, Junio C Hamano gits...@pobox.com wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
The code finds the changes of a commit, runs 'git blame' for each chunk
to see which other commits are relevant,
On Fri, Apr 19, 2013 at 2:24 PM, Junio C Hamano gits...@pobox.com wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
On Fri, Apr 19, 2013 at 12:08 PM, Junio C Hamano gits...@pobox.com wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
The code finds the changes of a commit,
Felipe Contreras felipe.contre...@gmail.com writes:
If this were _only_ to be used within send-email (i.e. replacing the
then send it out above with then use send-email to limit the
usecase), git cc-cmd would be a reasonable name. But if that is
the intended use case, it would even be more
Am 19.04.2013 21:24, schrieb Junio C Hamano:
Felipe Contreras felipe.contre...@gmail.com writes:
On Fri, Apr 19, 2013 at 12:08 PM, Junio C Hamano gits...@pobox.com wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
The code finds the changes of a commit, runs 'git blame' for each
Felipe Contreras felipe.contre...@gmail.com writes:
+File.open(file) do |f|
+ f.each do |line|
+case line
+when /^From (\h+) (.+)$/
+ from = $1
+when /^---\s+(\S+)/
+ source = $1 != '/dev/null' ? $1[2..-1] : nil
This may need to be
The code finds the changes of a commit, runs 'git blame' for each chunk
to see which other commits are relevant, and then reports the author and
signers.
Finally, it calculates what percentage of the total relevant commits
each person was involved in, and show only the ones that pass the
12 matches
Mail list logo
